Triple
T405426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sankaty Head Light |
E9372
|
entity |
| Predicate | focalHeight |
P9788
|
FINISHED |
| Object | approximately 158 feet above sea level |
—
|
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 158 feet above sea level | Statement: [Sankaty Head Light, focalHeight, approximately 158 feet above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focalHeight Context triple: [Sankaty Head Light, focalHeight, approximately 158 feet above sea level]
-
A.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
B.
heightWithPedestal
Indicates the total vertical measurement of an object including the height of its supporting pedestal.
-
C.
hasFocalRatioRange
Indicates that an entity is associated with a range of possible focal ratios, specifying the minimum and maximum f-number values it can have.
-
D.
hasHeight
chosen
Indicates that one entity possesses a specific vertical measurement or stature.
-
E.
originalHeight
Indicates the initial or starting height of an entity before any change, adjustment, or transformation occurs.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eca37fe881909802126952dfdd59 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e97066e8819083cc1b3a421b9650 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.