Triple
T1214487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pompey’s Pillar |
E26077
|
entity |
| Predicate | heightIncludingBase |
P1723
|
FINISHED |
| Object | about 28 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: about 28 metres | Statement: [Pompey’s Pillar, heightIncludingBase, about 28 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heightIncludingBase Context triple: [Pompey’s Pillar, heightIncludingBase, about 28 metres]
-
A.
heightWithPedestal
chosen
Indicates the total vertical measurement of an object including the height of its supporting pedestal.
-
B.
totalHeight
Indicates the combined vertical measurement resulting from adding the heights of one or more entities.
-
C.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
D.
heightReference
Indicates that one entity’s height is being measured, compared, or defined relative to another specified reference point or standard.
-
E.
heightClass
Indicates the categorical height level or range to which an entity is assigned (e.g., short, medium, tall).
- 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_69a4948331fc8190b531ac9bec71c491 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be0370b4819093618930f4eecfcc |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb62a7c08190a79dcb6ff72ac99b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.