Triple
T405419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sankaty Head Light |
E9372
|
entity |
| Predicate | originalLensOrder |
P11171
|
FINISHED |
| Object | first-order 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: first-order Fresnel lens | Statement: [Sankaty Head Light, originalLensOrder, first-order Fresnel lens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalLensOrder Context triple: [Sankaty Head Light, originalLensOrder, first-order Fresnel lens]
-
A.
subsequentOrder
Indicates that one order occurs after or follows another order in sequence.
-
B.
originallyOrderedBy
Indicates that one entity was the initial source or originator of an order or request for another entity.
-
C.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
-
D.
traditionalOrder
Indicates that entities are arranged or occur according to a customary, historically established sequence or hierarchy.
-
E.
usesOpticsType
Indicates that one entity employs or is characterized by a specific type of optical system or technology.
- 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_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. |
| PDg | Predicate description generation | batch_69a2ea60e590819081779a6510918d9b |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.