Triple
T7563983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jupiter Inlet Lighthouse |
E178863
|
entity |
| Predicate | yearDeactivated |
P58761
|
FINISHED |
| Object | N/A (still active) |
—
|
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: N/A (still active) | Statement: [Jupiter Inlet Lighthouse, yearDeactivated, N/A (still active)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearDeactivated Context triple: [Jupiter Inlet Lighthouse, yearDeactivated, N/A (still active)]
-
A.
deactivated
Indicates that an entity has been turned off, disabled, or rendered inactive so it no longer performs its usual function or role.
-
B.
lightDeactivatedYear
chosen
Indicates the year in which a light (or lighting system) was turned off, decommissioned, or otherwise taken out of active use.
-
C.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
D.
activeInYears
Indicates that an entity was active or operational during the specified years or year range.
-
E.
activeYearsEndTime
Indicates the point in time when an entity’s period of activity or operation comes to an end.
- 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_69c69f2f80288190b95cceb4da92ab2b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8fb1c00819096bdb73334d8d72e |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4dc485c819080da13e3b7f4f08f |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:50 p.m.