Triple
T26459701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amtrak Carl Sandburg |
E665594
|
entity |
| Predicate | ownerOfTrack |
P9942
|
FINISHED |
| Object | BNSF Railway |
—
|
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: BNSF Railway | Statement: [Amtrak Carl Sandburg, ownerOfTrack, BNSF Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerOfTrack Context triple: [Amtrak Carl Sandburg, ownerOfTrack, BNSF Railway]
-
A.
ownerOfSomeTrack
chosen
Indicates that an entity has ownership of at least one track (such as a song, audio track, or similar item).
-
B.
usesTrackOwnedBy
Indicates that an entity makes use of a track (e.g., route, path, or rail line) that is owned by another specified entity.
-
C.
ownerOfMostTrack
Indicates that the subject is the owner of the greatest number of tracks in a given collection or context, compared to all other potential owners.
-
D.
associatedWithTrack
Indicates a relationship in which an entity is linked or connected to a specific track, such as being part of, derived from, or relevant to that track.
-
E.
accessedByTrack
Indicates that something (such as a location, resource, or object) is reachable or entered via a particular track or pathway.
- F. None of above.
Provenance (3 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 12:11 a.m.