Triple
T12056082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape St Blaize Lighthouse |
E287045
|
entity |
| Predicate | focalHeightMeters |
P61254
|
FINISHED |
| Object | 73 |
—
|
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: 73 | Statement: [Cape St Blaize Lighthouse, focalHeightMeters, 73]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focalHeightMeters Context triple: [Cape St Blaize Lighthouse, focalHeightMeters, 73]
-
A.
focalLength
Indicates the distance between a lens or mirror and its focal point, determining how strongly it converges or diverges light.
-
B.
focalPlaneHeight
chosen
Indicates the vertical distance or elevation of the focal plane relative to a defined reference level or surface.
-
C.
depthMetresApprox
Indicates an approximate measurement of how deep something is in metres, rather than an exact value.
-
D.
hasFocalRatio
Indicates a relationship where an optical system is associated with a specific focal ratio (f-number) that characterizes its light-gathering speed and image brightness.
-
E.
hasFocalPlane
Indicates that an optical system or imaging device possesses a specific focal plane where light is brought into focus.
- 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bda47c8190b94860b31df4a98c |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.