Triple
T16747086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSAP |
E406983
|
entity |
| Predicate | roleInFrame |
P124485
|
FINISHED |
| Object | selects destination service access point |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: selects destination service access point | Statement: [DSAP, roleInFrame, selects destination service access point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFrame Context triple: [DSAP, roleInFrame, selects destination service access point]
-
A.
roleInScene
Indicates that an entity participates in a particular scene with a specific role or function within that scene.
-
B.
roleInGrid
Indicates the specific function or position an entity occupies within a structured grid or matrix.
-
C.
roleInMovement
Indicates the specific function, position, or contribution an entity has within a broader movement or collective effort.
-
D.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
E.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa2311748190a17416de577ad159 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:21 a.m.