Triple
T5803283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trellick Tower |
E128678
|
entity |
| Predicate | hasSeparateServiceTower |
P8955
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Trellick Tower, hasSeparateServiceTower, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeparateServiceTower Context triple: [Trellick Tower, hasSeparateServiceTower, true]
-
A.
hasCommunicationTowers
Indicates that one entity possesses, contains, or is equipped with communication towers used for transmitting or receiving signals.
-
B.
hasTower
chosen
Indicates that one entity possesses, contains, or is characterized by the presence of a tower.
-
C.
hasSatelliteTerminal
Indicates that an entity is equipped with or connected to a satellite communication terminal.
-
D.
hasTowerHeight
Indicates that an entity (such as a tower or structure) has a specific height value associated with it.
-
E.
hasSeparateUnit
Indicates that one entity exists or is treated as an independent, distinct unit from another 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_69c00846a0d881909e46841f8e156b64 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1304588190b59a18fb7b70a60f |
completed | March 22, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69c021d477008190946113f9859eeb90 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:52 p.m.