Triple
T28183735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Færder Lighthouse |
E716110
|
entity |
| Predicate | previousLightEstablished |
P64595
|
FINISHED |
| Object | 1697 |
—
|
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: 1697 | Statement: [Færder Lighthouse, previousLightEstablished, 1697]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousLightEstablished Context triple: [Færder Lighthouse, previousLightEstablished, 1697]
-
A.
previousLightStations
chosen
Indicates that one light station existed earlier in time or sequence than another related light station.
-
B.
replacedEarlierLight
Indicates that one light source has been substituted or superseded by another light source that existed or was installed earlier in time.
-
C.
laterLightSource
Indicates that one light source occurs or is activated after another in time.
-
D.
previousProtectionEstablished
Indicates that a protective measure or status had already been put in place prior to the current point in time or event.
-
E.
expectedFirstLight
Indicates the anticipated time or occurrence of the first appearance of light, such as dawn or initial illumination, in a given 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 27, 2026, 10:21 p.m.