Triple
T6149210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Street surface section |
E137154
|
entity |
| Predicate | isAboveGround |
P11729
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Washington Street surface section, isAboveGround, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAboveGround Context triple: [Washington Street surface section, isAboveGround, true]
-
A.
heightAboveGround
Indicates the vertical distance of an entity measured from the ground surface directly beneath it.
-
B.
usesGroundSystem
Indicates that one entity operates, relies on, or interacts with a particular ground-based system to perform its functions or services.
-
C.
isElevatedOrAtGradeIn
chosen
Indicates that one entity is positioned either above ground level (elevated) or directly at ground level (at grade) within the context of another entity or environment.
-
D.
hasGroundFloor
Indicates that a building or structure includes a ground-level floor as part of its layout or design.
-
E.
heightAboveSurroundings
Indicates that an entity’s vertical position or elevation is higher than that of its immediate surrounding area.
- 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_69c008a2c6308190a56519b22d55d083 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05ce21820819096be9159d6b70a5f |
completed | March 22, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:16 p.m.