Triple
T7975353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McGulpin Point Lighthouse |
E185429
|
entity |
| Predicate | deactivatedYear |
P58761
|
FINISHED |
| Object | 1906 |
—
|
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: 1906 | Statement: [McGulpin Point Lighthouse, deactivatedYear, 1906]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deactivatedYear Context triple: [McGulpin Point Lighthouse, deactivatedYear, 1906]
-
A.
lightDeactivatedYear
chosen
Indicates the year in which a light (or lighting system) was turned off, decommissioned, or otherwise taken out of active use.
-
B.
deactivated
Indicates that an entity has been turned off, disabled, or rendered inactive so it no longer performs its usual function or role.
-
C.
exitYear
Indicates the year in which an entity leaves, finishes, or ceases its association with another entity or context.
-
D.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
E.
discontinuationAnnouncementYear
Indicates the year in which the discontinuation of something (such as a product, service, or program) was officially announced.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bf42a508190bb661fce34ec0151 |
completed | March 31, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69cb047a8e4c81909b79e0f0bf56440c |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:14 p.m.