Triple
T22857349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pomposa Abbey |
E566818
|
entity |
| Predicate | hasBellTowerHeightApprox |
P18664
|
FINISHED |
| Object | 48 meters |
—
|
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: 48 meters | Statement: [Pomposa Abbey, hasBellTowerHeightApprox, 48 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBellTowerHeightApprox Context triple: [Pomposa Abbey, hasBellTowerHeightApprox, 48 meters]
-
A.
hasBellTower
Indicates that one entity (typically a building or structure) possesses or includes a bell tower as part of it.
-
B.
hasBellTowerHeightSignificance
Indicates that the height of a bell tower holds particular importance or relevance in a given context or relationship.
-
C.
hasBellTowerLocation
Indicates the specific location where a bell tower is situated or attached relative to another structure or place.
-
D.
hasTowerHeight
chosen
Indicates that an entity (such as a tower or structure) has a specific height value associated with it.
-
E.
hasMinaretHeightApprox
Indicates that an entity has a minaret whose height is approximately a specified value, allowing for some margin of imprecision.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17ebd7d48819085f350f2ce4144a0 |
completed | April 29, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:37 p.m.