Triple
T18958225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell Rock reef |
E463836
|
entity |
| Predicate | hasLighthouseSince |
P117141
|
FINISHED |
| Object | 1811 |
—
|
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: 1811 | Statement: [Bell Rock reef, hasLighthouseSince, 1811]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLighthouseSince Context triple: [Bell Rock reef, hasLighthouseSince, 1811]
-
A.
hasLightHouse
Indicates that one place or structure possesses, contains, or is associated with a lighthouse.
-
B.
lighthouseAutomated
Indicates that a lighthouse operates automatically without the need for on-site human keepers.
-
C.
lighthouseBuiltIn
chosen
Indicates that a lighthouse was constructed or established in a specific location or during a specific time period.
-
D.
lighthouseStatus
Indicates the operational condition or state (e.g., active, inactive, under maintenance) of a lighthouse at a given time.
-
E.
lighthouseFunction
Indicates that an entity serves as a lighthouse, providing navigational guidance or warning signals to other entities (such as ships or aircraft).
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5d057a48190b82b5788b3281e28 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon