Triple
T375061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broad Street Station (Philadelphia) |
E8352
|
entity |
| Predicate | trainShedType |
P13070
|
FINISHED |
| Object | iron and glass train shed |
—
|
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: iron and glass train shed | Statement: [Broad Street Station (Philadelphia), trainShedType, iron and glass train shed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainShedType Context triple: [Broad Street Station (Philadelphia), trainShedType, iron and glass train shed]
-
A.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
B.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
C.
rollingStockType
Indicates the specific category or type of railway rolling stock associated with an entity (e.g., locomotive, passenger car, freight wagon).
-
D.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
E.
terminusType
Indicates the specific kind or role of an endpoint or terminal within a route, network, or process.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec1585648190943f1c698e9b2d81 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e96216048190873ae533fa5b864d |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ebcb1b2c8190a68bb3bad600c227 |
completed | Feb. 28, 2026, 1:21 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.