Triple
T15669560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sturgeon Bay Ship Canal Light |
E377270
|
entity |
| Predicate | originalOptic |
P7239
|
FINISHED |
| Object | Fresnel lens |
—
|
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: Fresnel lens | Statement: [Sturgeon Bay Ship Canal Light, originalOptic, Fresnel lens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalOptic Context triple: [Sturgeon Bay Ship Canal Light, originalOptic, Fresnel lens]
-
A.
originalLens
Indicates that one lens is the initial or source lens from which another lens or lens configuration is derived or referenced.
-
B.
usesOpticsType
chosen
Indicates that one entity employs or is characterized by a specific type of optical system or technology.
-
C.
opticalDesign
Indicates a relationship where one entity is responsible for creating, specifying, or defining the optical configuration or characteristics of another entity.
-
D.
originalLensOrder
Indicates that one lens precedes another in the original, intended ordering of lenses.
-
E.
objectiveLensDiameter
Indicates the diameter of the objective lens used in an optical device, such as a camera or telescope.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f1254508190a77a16b7bfd299ad |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.