Triple
T33673286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Filtvet Lighthouse |
E862682
|
entity |
| Predicate | lightSector |
P177188
|
FINISHED |
| Object | directional sectors for navigation in Oslofjord |
—
|
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: directional sectors for navigation in Oslofjord | Statement: [Filtvet Lighthouse, lightSector, directional sectors for navigation in Oslofjord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightSector Context triple: [Filtvet Lighthouse, lightSector, directional sectors for navigation in Oslofjord]
-
A.
lightPath
Indicates the route or trajectory that light follows as it travels between entities or through a medium.
-
B.
lightName
Indicates the designated name or label assigned to a specific light or lighting element.
-
C.
lightType
Indicates the specific category or kind of light associated with an entity or lighting setup.
-
D.
lightSourceFor
Indicates that one entity serves as the source of illumination for another entity.
-
E.
lightFunction
Indicates that one entity serves as a source or means of illumination or lighting for another entity or context.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fae2a7a8819099945d1706a94bfd |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fa335b908190a20d92d5396203b5 |
completed | May 3, 2026, 7:33 a.m. |
Created at: May 1, 2026, 1:43 a.m.