Triple
T6277345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mott Avenue Portal |
E140693
|
entity |
| Predicate | belowGroundSectionType |
P15152
|
FINISHED |
| Object | subway tunnel |
—
|
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: subway tunnel | Statement: [Mott Avenue Portal, belowGroundSectionType, subway tunnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belowGroundSectionType Context triple: [Mott Avenue Portal, belowGroundSectionType, subway tunnel]
-
A.
elevationBelowGround
Indicates that one entity’s elevation is located beneath the ground surface or reference ground level.
-
B.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
C.
subterranean
Indicates that one entity is located beneath the surface of the ground or under another structure or area.
-
D.
hasUndergroundSection
chosen
Indicates that an entity includes a portion or segment that is located below ground level.
-
E.
basementType
Indicates the type or classification of a building’s basement as defined in the relationship.
- 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_69c008cc158881908df6ec94a911c736 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063d96fbc8190a9091456b82762d1 |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c05608a5608190b22a1fdc4060470d |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:26 p.m.