Triple
T22330148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Building No. 21 |
E552001
|
entity |
| Predicate | directorElevatorOfficeAreaInSquareMeters |
P147777
|
FINISHED |
| Object | about 6 |
—
|
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: about 6 | Statement: [Building No. 21, directorElevatorOfficeAreaInSquareMeters, about 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directorElevatorOfficeAreaInSquareMeters Context triple: [Building No. 21, directorElevatorOfficeAreaInSquareMeters, about 6]
-
A.
officeIsIn
Indicates that one office is located within or inside another specified place or building.
-
B.
locatedInSkyscraper
Indicates that one entity is physically situated within or inside a skyscraper.
-
C.
hasNumberOfElevatorBanks
Indicates the relationship specifying how many distinct elevator banks are present in or associated with a given entity.
-
D.
typeOfBuildingSpace
Indicates the specific kind or category of building space that an entity represents or occupies.
-
E.
hasOfficeFloors
Indicates that one entity (typically a building or structure) contains floors that are designated or used as office space.
- F. None of above. chosen
Provenance (4 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1577a9c348190b8662142afa832be |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:43 p.m.