Triple
T28459846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City Subway Line 5 |
E720119
|
entity |
| Predicate | maintenanceFacilityUsed |
P41182
|
FINISHED |
| Object | IRT maintenance shops (various) |
—
|
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: IRT maintenance shops (various) | Statement: [New York City Subway Line 5, maintenanceFacilityUsed, IRT maintenance shops (various)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintenanceFacilityUsed Context triple: [New York City Subway Line 5, maintenanceFacilityUsed, IRT maintenance shops (various)]
-
A.
hasMaintenanceFacilities
Indicates that one entity provides or contains facilities where the other entity can be serviced, repaired, or maintained.
-
B.
maintenanceType
Indicates the specific category or kind of maintenance activity associated with an entity or relationship.
-
C.
maintenanceAuthority
Indicates that one entity has the responsibility or official power to maintain, service, or keep another entity in proper working condition.
-
D.
maintenanceFeature
Indicates that one entity serves as a maintenance-related feature, capability, or component associated with another entity.
-
E.
usedFacilityName
chosen
Indicates that an entity made use of a facility identified by a particular name.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 2:38 a.m.