Triple
T3642555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PRR T1 |
E77221
|
entity |
| Predicate | prototypeRoadNumbers |
P28807
|
FINISHED |
| Object | 6110 |
—
|
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: 6110 | Statement: [PRR T1, prototypeRoadNumbers, 6110]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prototypeRoadNumbers Context triple: [PRR T1, prototypeRoadNumbers, 6110]
-
A.
routeNumber
Indicates the specific identifying number assigned to a route within a transportation or delivery network.
-
B.
numberOfRoadways
chosen
Indicates the count of distinct roadways associated with or present at a given entity or location.
-
C.
hasRoadConfiguration
Indicates that there exists a specific arrangement or layout of roads associated with or characterizing an entity.
-
D.
roadNumberingZone
Indicates the designated numbering zone or area within which a particular road’s identification or route number is assigned.
-
E.
roadName
Indicates the specific name assigned to a road that identifies it within a transportation or address system.
- 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc359a91481908aef1c022f45e55c |
completed | March 8, 2026, 6:43 p.m. |
| PD | Predicate disambiguation | batch_69adb8445b2c8190ab07f6ad4e010d0e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.