Triple
T15117033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telecom Tower |
E361066
|
entity |
| Predicate | isObservationDeckHeight |
P5396
|
FINISHED |
| Object | approximately 150 metres |
—
|
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: approximately 150 metres | Statement: [Telecom Tower, isObservationDeckHeight, approximately 150 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isObservationDeckHeight Context triple: [Telecom Tower, isObservationDeckHeight, approximately 150 metres]
-
A.
observationDeckHeight
chosen
Indicates the vertical distance of an observation deck above a reference level, typically the ground or sea level.
-
B.
hasObservationDeckName
Indicates that an observation deck is associated with a specific name or title.
-
C.
hasObservationDeckAccess
Indicates that an entity is permitted to enter or use an observation deck.
-
D.
hasObservationDeckStatus
Indicates whether something possesses an observation deck and, if so, what its current status or condition is.
-
E.
numberOfObservationDecks
Indicates the count of observation decks associated with or present in an entity.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0059ca9048190b742e70e818ee64f |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:05 a.m.