Triple
T25583822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NC By Train |
E641324
|
entity |
| Predicate | promotesRoute |
P161655
|
FINISHED |
| Object | Piedmont (Amtrak train) |
—
|
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: Piedmont (Amtrak train) | Statement: [NC By Train, promotesRoute, Piedmont (Amtrak train)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotesRoute Context triple: [NC By Train, promotesRoute, Piedmont (Amtrak train)]
-
A.
promotesFrom
Indicates that one entity advances or elevates another entity from a lower position, role, or status to a higher one.
-
B.
promotionPath
Indicates the career advancement relationship showing how one role or position can lead or progress to another.
-
C.
promotes
Indicates that one entity actively supports, advances, or encourages the growth, adoption, or success of another entity or outcome.
-
D.
parallelRoute
Indicates that one route runs alongside and in the same general direction as another route without intersecting it.
-
E.
connectedRoute
Indicates that there is a direct or logically continuous path linking two locations or segments within a network.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6200ac60481909895c61d050b1338 |
completed | May 2, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 21, 2026, 4:14 p.m.