Triple
T7639066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOSPR concert hall |
E172952
|
entity |
| Predicate | hasNumberOfStoreysBelowGround |
P996
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [NOSPR concert hall, hasNumberOfStoreysBelowGround, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfStoreysBelowGround Context triple: [NOSPR concert hall, hasNumberOfStoreysBelowGround, 1]
-
A.
numberOfBasementLevels
chosen
Indicates the total count of basement levels associated with a given structure or property.
-
B.
hasBasement
Indicates that a building or structure includes a basement level as part of its physical layout.
-
C.
hasGroundFloor
Indicates that a building or structure includes a ground-level floor as part of its layout or design.
-
D.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
E.
hasLowerFloor
Indicates that one location, structure, or level includes or is directly connected to a floor situated below another floor.
- 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6facb14188190952de18fa2699784 |
completed | March 27, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:57 p.m.