Triple
T7841765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Village – Metropolitan Avenue |
E181820
|
entity |
| Predicate | hasYardConnection |
P18851
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Middle Village – Metropolitan Avenue, hasYardConnection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYardConnection Context triple: [Middle Village – Metropolitan Avenue, hasYardConnection, yes]
-
A.
hasYard
Indicates that one entity possesses or includes a yard as part of its property or premises.
-
B.
hasGoodsYard
Indicates that a location or facility includes or is equipped with a goods yard for handling freight or cargo.
-
C.
connectsToMainLineAt
Indicates that one entity is linked or joined to a primary or central line at a specific point.
-
D.
hasRailYard
chosen
Indicates that one entity possesses, contains, or includes a rail yard as part of its facilities or infrastructure.
-
E.
hasAirsideConnection
Indicates that there is a direct, secure connection between areas past security (airside) of two locations, allowing passengers to transfer without re-clearing security or immigration.
- 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_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb14c6cbe48190b73df491de1004c3 |
completed | March 31, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:48 p.m.