Triple
T13400558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turning Torso |
E319815
|
entity |
| Predicate | storeyCountBelowGround |
P996
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Turning Torso, storeyCountBelowGround, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storeyCountBelowGround Context triple: [Turning Torso, storeyCountBelowGround, 2]
-
A.
numberOfBasementLevels
chosen
Indicates the total count of basement levels associated with a given structure or property.
-
B.
hasUndergroundLevel
Indicates that one entity possesses or includes a level, floor, or section that is located below ground level.
-
C.
hasFloorsAboveGround
Indicates that an entity (typically a building or structure) possesses a specified number of floors that are located above ground level.
-
D.
floorCountIncludingBasement
Indicates the total number of floors in a building, counting all above-ground levels plus any basement levels.
-
E.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbae47e99081909d8b5dba97a11988 |
completed | April 12, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:34 p.m.