Triple
T36161970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buckingham Branch Railroad |
E1045901
|
entity |
| Predicate | leasesTrackFrom |
P184974
|
FINISHED |
| Object | CSX Transportation |
—
|
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: CSX Transportation | Statement: [Buckingham Branch Railroad, leasesTrackFrom, CSX Transportation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leasesTrackFrom Context triple: [Buckingham Branch Railroad, leasesTrackFrom, CSX Transportation]
-
A.
trackFrom
Indicates a source or origin from which something is tracked or monitored.
-
B.
trackOver
Indicates that one entity follows, monitors, or records the behavior, state, or progress of another entity across a period of time or over a sequence of events.
-
C.
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.
-
D.
track
Indicates that one entity follows, monitors, or keeps a record of another entity’s state, behavior, or progress over time.
-
E.
trackUsed
Indicates that a particular track (such as a route, path, or media track) has been utilized or selected in a given context.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b69a74a08190b31b1201278a2c57 |
completed | May 3, 2026, 8:56 p.m. |
Created at: May 3, 2026, 4:08 p.m.