Triple
T35728178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 7 Flushing Local |
E1032672
|
entity |
| Predicate | maintenanceDepot |
P14646
|
FINISHED |
| Object | Corona Yard |
—
|
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: Corona Yard | Statement: [7 Flushing Local, maintenanceDepot, Corona Yard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintenanceDepot Context triple: [7 Flushing Local, maintenanceDepot, Corona Yard]
-
A.
maintenanceOrganization
Indicates the organization responsible for performing or overseeing maintenance activities on the associated entity.
-
B.
depot
chosen
Indicates that an entity serves as a storage or distribution center location for another entity, such as goods, vehicles, or resources.
-
C.
maintenanceType
Indicates the specific category or kind of maintenance activity associated with an entity or relationship.
-
D.
maintenanceAuthority
Indicates that one entity has the responsibility or official power to maintain, service, or keep another entity in proper working condition.
-
E.
maintenanceRole
Indicates that one entity has a responsibility or function related to maintaining, servicing, or upkeeping another entity.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:05 p.m.