Triple
T3941822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europaturm |
E92049
|
entity |
| Predicate | hasBaseDiameter |
P25056
|
FINISHED |
| Object | approximately 59 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 59 metres | Statement: [Europaturm, hasBaseDiameter, approximately 59 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaseDiameter Context triple: [Europaturm, hasBaseDiameter, approximately 59 metres]
-
A.
shaftDiameterAtBase
chosen
Indicates the diameter measurement of a shaft specifically at its base portion.
-
B.
approximateDiameter
Indicates that one entity specifies the estimated or rough measurement of another entity’s diameter.
-
C.
baseCircumference
Indicates the circumference measurement of the base of an object or geometric figure.
-
D.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
E.
hasTypicalColumnHeightToDiameterRatio
Indicates that there is a characteristic or commonly observed proportional relationship between a column’s height and its diameter.
- 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee764235081909309b3c982f322a9 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.