Triple
T5073747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Gratiot Lighthouse |
E114341
|
entity |
| Predicate | focalPlaneHeight |
P61254
|
FINISHED |
| Object | approximately 82 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 82 feet | Statement: [Fort Gratiot Lighthouse, focalPlaneHeight, approximately 82 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focalPlaneHeight Context triple: [Fort Gratiot Lighthouse, focalPlaneHeight, approximately 82 feet]
-
A.
hasFocalPlane
Indicates that an optical system or imaging device possesses a specific focal plane where light is brought into focus.
-
B.
focalLength
Indicates the distance between a lens or mirror and its focal point, determining how strongly it converges or diverges light.
-
C.
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.
-
D.
maximumWorkingDistance
Indicates the greatest allowable or effective distance at which the specified work, operation, or interaction can be performed.
-
E.
shaftHeight
Indicates the vertical extent or length of a shaft from its base to its top.
- F. None of above. chosen
Provenance (4 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_69bd443cf28c8190ad371d603563dbdd |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74d0be1c819081b26235fe602a30 |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd73d90b608190bd6c2407e84e2b64 |
completed | March 20, 2026, 4:20 p.m. |
Created at: March 20, 2026, 1:39 p.m.