Triple
T21931344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brock Commons Tallwood House |
E541573
|
entity |
| Predicate | aboveGroundStoreys |
P78480
|
FINISHED |
| Object | 18 |
—
|
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: 18 | Statement: [Brock Commons Tallwood House, aboveGroundStoreys, 18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aboveGroundStoreys Context triple: [Brock Commons Tallwood House, aboveGroundStoreys, 18]
-
A.
hasFloorsAboveGround
chosen
Indicates that an entity (typically a building or structure) possesses a specified number of floors that are located above ground level.
-
B.
locatedAboveGround
Indicates that one entity is positioned at a level higher than the ground surface, not buried or below ground.
-
C.
floorCountOfSurroundingBuildings
Indicates the number of floors in the buildings that are located around or near a given reference building or area.
-
D.
floorCount
Indicates the number of floors or levels that a building or structure has.
-
E.
hasUpperFloor
Indicates that one entity possesses or includes an upper floor relative to another level or reference point.
- 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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f123ff16148190843d92bbc1e9bb24 |
completed | April 28, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:47 p.m.