Triple
T1608943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ten Pound Island Light |
E34571
|
entity |
| Predicate | hasFocalHeight |
P21256
|
FINISHED |
| Object | approximately 56 feet |
—
|
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 56 feet | Statement: [Ten Pound Island Light, hasFocalHeight, approximately 56 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFocalHeight Context triple: [Ten Pound Island Light, hasFocalHeight, approximately 56 feet]
-
A.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
B.
hasFocalPlane
chosen
Indicates that an optical system or imaging device possesses a specific focal plane where light is brought into focus.
-
C.
heightReference
Indicates that one entity’s height is being measured, compared, or defined relative to another specified reference point or standard.
-
D.
hasUpperBarLength
Indicates that an entity possesses an upper bar whose length is specified or constrained by the related value or object.
-
E.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
- 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_69a885fea6a481909fe83ba6441f1774 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fa6926081908bc78d15c0be3185 |
completed | March 5, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69a907c35f848190a2428c52e81d013e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.