Triple
T36675425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AC-9 articulated steam locomotives |
E905528
|
entity |
| Predicate | assignedService |
P186155
|
FINISHED |
| Object | El Paso–Tucumcari line |
—
|
NE NERFINISHED |
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: El Paso–Tucumcari line | Statement: [AC-9 articulated steam locomotives, assignedService, El Paso–Tucumcari line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assignedService Context triple: [AC-9 articulated steam locomotives, assignedService, El Paso–Tucumcari line]
-
A.
assignedAs
Indicates that one entity is designated or appointed to perform a specific role, task, or function in relation to another entity.
-
B.
assignedUnder
Indicates that one entity has been given responsibility, duty, or authority to act within the scope, supervision, or framework defined by another entity.
-
C.
assignedTo
Indicates that responsibility for a task, item, or role has been designated to a specific entity.
-
D.
assignedFunction
Indicates that a specific role, duty, or function has been formally allocated to an entity.
-
E.
assignedToWorkBy
Indicates that one entity is designated or directed by another entity to perform a specific job, task, or role.
- 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:12 p.m.