Triple
T3554410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panhandle Bridge |
E75184
|
entity |
| Predicate | formerlyCarried |
P23508
|
FINISHED |
| Object | Pennsylvania Railroad passenger trains |
—
|
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: Pennsylvania Railroad passenger trains | Statement: [Panhandle Bridge, formerlyCarried, Pennsylvania Railroad passenger trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlyCarried Context triple: [Panhandle Bridge, formerlyCarried, Pennsylvania Railroad passenger trains]
-
A.
carriedBy
Indicates that one entity is physically supported and transported by another entity.
-
B.
carriedTo
Indicates that one entity transported or conveyed another entity from one place to another.
-
C.
carriedFrom
Indicates that something was transported or moved away starting from a specified source location or origin.
-
D.
alsoCarries
Indicates that an entity, in addition to other items or responsibilities it has, carries another specified item or load as well.
-
E.
usedToBe
chosen
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc05549d88190acdebdd542ea1a67 |
completed | March 8, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69adb83270ac819083967db0570167d2 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:20 p.m.