Triple
T36747120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longwood (historic house) |
E907796
|
entity |
| Predicate | numberOfStoreysBelowGround |
P203452
|
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: [Longwood (historic house), numberOfStoreysBelowGround, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfStoreysBelowGround Context triple: [Longwood (historic house), numberOfStoreysBelowGround, 1]
-
A.
numberOfStoreysUnderground
chosen
Indicates the count of levels or storeys of a structure that are located below ground level.
-
B.
numberOfBasementLevels
Indicates the total count of basement levels associated with a given structure or property.
-
C.
hasUndergroundLevel
Indicates that one entity possesses or includes a level, floor, or section that is located below ground level.
-
D.
floorCountIncludingBasement
Indicates the total number of floors in a building, counting all above-ground levels plus any basement levels.
-
E.
hasFloorsAboveGround
Indicates that an entity (typically a building or structure) possesses a specified number of floors that are located above ground level.
- 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_69f76e76d10881909ec1679bc043108c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.