Triple
T14260036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuwait Telecommunications Tower |
E353487
|
entity |
| Predicate | hasBaseBuildingFloors |
P113473
|
FINISHED |
| Object | several office floors |
—
|
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: several office floors | Statement: [Kuwait Telecommunications Tower, hasBaseBuildingFloors, several office floors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaseBuildingFloors Context triple: [Kuwait Telecommunications Tower, hasBaseBuildingFloors, several office floors]
-
A.
hasFloorsAboveGround
Indicates that an entity (typically a building or structure) possesses a specified number of floors that are located above ground level.
-
B.
numberOfFloors
Indicates the total count of distinct floor levels that a building or structure has.
-
C.
numberOfBasementLevels
Indicates the total count of basement levels associated with a given structure or property.
-
D.
hasResidentialFloors
Indicates that an entity (such as a building or structure) includes one or more floors designated for residential use.
-
E.
numberOfResidentialFloors
Indicates the total count of floors in a building that are designated for residential use.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de635534988190816fdfb315cd2a3f |
completed | April 14, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:09 a.m.