Triple
T18719550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittsburgh and Lake Erie Railroad |
E457731
|
entity |
| Predicate | servedFacilityType |
P2836
|
FINISHED |
| Object | steel mills |
—
|
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: steel mills | Statement: [Pittsburgh and Lake Erie Railroad, servedFacilityType, steel mills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedFacilityType Context triple: [Pittsburgh and Lake Erie Railroad, servedFacilityType, steel mills]
-
A.
servesFacility
Indicates that one entity provides services or support to a particular facility as its client, target, or area of operation.
-
B.
designedFacilityType
Indicates the type or category of facility that something (such as a plan, system, or component) is specifically designed for.
-
C.
hasFacilityType
chosen
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
D.
fccFacilityType
Indicates the specific type or classification of a facility as defined by the FCC (Federal Communications Commission).
-
E.
servesTransitFacility
Indicates that one entity provides service or operational support to a transit facility, such as a station, stop, or terminal.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56ab90adc81909f3b4aabb6d5a707 |
completed | April 19, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69e478e0889c8190a118d67b200ce8ef |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.