Triple
T35328212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kista, Stockholm |
E1020249
|
entity |
| Predicate | hasHighRiseBuilding |
P114769
|
FINISHED |
| Object | Kista Science Tower |
—
|
NE NERFINISHED |
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: Kista Science Tower | Statement: [Kista, Stockholm, hasHighRiseBuilding, Kista Science Tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighRiseBuilding Context triple: [Kista, Stockholm, hasHighRiseBuilding, Kista Science Tower]
-
A.
hasHighRiseBuildings
chosen
Indicates that the subject location contains one or more tall, multi-story buildings commonly classified as high-rises.
-
B.
isHighRise
Indicates that a building or structure is classified as a high-rise, typically due to its height exceeding a defined multi-story threshold.
-
C.
hasHighRiseSpan
Indicates that a structure or element extends vertically across a significant number of levels or stories, forming a tall or high-rise span.
-
D.
hasUpperFloor
Indicates that one entity possesses or includes an upper floor relative to another level or reference point.
-
E.
hasTowerHeight
Indicates that an entity (such as a tower or structure) has a specific height value associated with it.
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
Created at: May 3, 2026, 4:03 p.m.