Triple
T22698502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Cathedral of Cuenca |
E561248
|
entity |
| Predicate | towerHeightStatus |
P30757
|
FINISHED |
| Object | towers were left low to avoid structural risk |
—
|
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: towers were left low to avoid structural risk | Statement: [New Cathedral of Cuenca, towerHeightStatus, towers were left low to avoid structural risk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: towerHeightStatus Context triple: [New Cathedral of Cuenca, towerHeightStatus, towers were left low to avoid structural risk]
-
A.
towerStatus
Indicates the current operational or structural condition of a tower within a given system or context.
-
B.
towerLocation
Indicates that a tower is located at, or associated with, a specific place or geographic location.
-
C.
towerName
Indicates the specific name assigned to a tower in the relationship.
-
D.
hasTowerHeight
Indicates that an entity (such as a tower or structure) has a specific height value associated with it.
-
E.
buildingHeightContext
chosen
Indicates the contextual or situational factors under which a building’s height is defined, measured, or interpreted.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178a008448190b393335704128fe8 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:14 p.m.