Triple
T31851130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seahenge |
E813066
|
entity |
| Predicate | centralStumpDiameter |
P175221
|
FINISHED |
| Object | approximately 1.5 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: approximately 1.5 meters | Statement: [Seahenge, centralStumpDiameter, approximately 1.5 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralStumpDiameter Context triple: [Seahenge, centralStumpDiameter, approximately 1.5 meters]
-
A.
maximumTrunkDiameter
Indicates the largest thickness of a trunk measured across its widest point.
-
B.
shaftDiameterAtBase
Indicates the diameter measurement of a shaft specifically at its base portion.
-
C.
trunkDiameter
Indicates the measured thickness of a trunk, typically expressed as the diameter across its cross-section.
-
D.
centralZoneDiameter
chosen
Indicates the diameter measurement of the central zone of an object or region, typically from one side of the central area directly across to the opposite side.
-
E.
structureDiameter
Indicates the measured diameter or width of a given structure.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 30, 2026, 11:51 p.m.