Triple
T19490586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nash Point Lighthouse |
E487636
|
entity |
| Predicate | fogSignalStatus |
P136115
|
FINISHED |
| Object | decommissioned |
—
|
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: decommissioned | Statement: [Nash Point Lighthouse, fogSignalStatus, decommissioned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fogSignalStatus Context triple: [Nash Point Lighthouse, fogSignalStatus, decommissioned]
-
A.
hasFogSignal
Indicates that an entity is equipped with or associated with a fog signal used for navigation or warning in low-visibility conditions.
-
B.
lighthouseStatus
Indicates the operational condition or state (e.g., active, inactive, under maintenance) of a lighthouse at a given time.
-
C.
lighthouseColor
Indicates the color attribute associated with a lighthouse.
-
D.
hasHazardSignage
Indicates that appropriate warning or hazard signs are present to alert people to potential dangers associated with the entity.
-
E.
hasTrafficSignals
Indicates that traffic control signals are present at or associated with a given location or roadway feature.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6348d43448190bf83680522b8b415 |
completed | April 20, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004d3a708190a1c13c8f644f3926 |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:39 p.m.