Triple
T15330295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Cathedral |
E366514
|
entity |
| Predicate | hasTowerHeightMetres |
P18664
|
FINISHED |
| Object | approximately 135 |
—
|
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 135 | Statement: [New Cathedral, hasTowerHeightMetres, approximately 135]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTowerHeightMetres Context triple: [New Cathedral, hasTowerHeightMetres, approximately 135]
-
A.
hasTowerHeight
chosen
Indicates that an entity (such as a tower or structure) has a specific height value associated with it.
-
B.
testTowerHeight
Indicates that an entity measures or evaluates the height of a tower.
-
C.
buildingHeightContext
Indicates the contextual or situational factors under which a building’s height is defined, measured, or interpreted.
-
D.
hasTower
Indicates that one entity possesses, contains, or is characterized by the presence of a tower.
-
E.
buildingHeight
Indicates the vertical extent or height measurement of a building.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e0161ac8190aa1d52c063c02ad0 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.