Triple
T34167580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oranjemolen lighthouse |
E876452
|
entity |
| Predicate | lightPurpose |
P129699
|
FINISHED |
| Object | aid to navigation in Western Scheldt estuary |
—
|
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: aid to navigation in Western Scheldt estuary | Statement: [Oranjemolen lighthouse, lightPurpose, aid to navigation in Western Scheldt estuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightPurpose Context triple: [Oranjemolen lighthouse, lightPurpose, aid to navigation in Western Scheldt estuary]
-
A.
illuminationPurpose
Indicates that one entity serves the purpose of providing light or illumination for another entity or context.
-
B.
lightType
Indicates the specific category or kind of light associated with an entity or lighting setup.
-
C.
lightOrganFunction
Indicates that one entity serves as the functional light-producing organ or structure for another entity.
-
D.
lightSourceFor
Indicates that one entity serves as the source of illumination for another entity.
-
E.
lightFunction
chosen
Indicates that one entity serves as a source or means of illumination or lighting for another entity or context.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fe0aa4881908023119b94d9fcbe |
completed | May 3, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.