Triple
T20271988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Souter Lighthouse |
E499115
|
entity |
| Predicate | decommissionedAsLighthouse |
P139499
|
FINISHED |
| Object | 1988 |
—
|
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: 1988 | Statement: [Souter Lighthouse, decommissionedAsLighthouse, 1988]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decommissionedAsLighthouse Context triple: [Souter Lighthouse, decommissionedAsLighthouse, 1988]
-
A.
thirdLighthouseDecommissioned
Indicates that the third lighthouse in a specified sequence or group has been officially taken out of service.
-
B.
lighthouseConstructedIn
Indicates that a lighthouse was built or established during a specific time period or in a specific year.
-
C.
decommissionedBy
Indicates that an entity was formally taken out of service or use by a specific agent or authority.
-
D.
decommissionedWith
Indicates that an entity was taken out of service or retired in conjunction with, or as part of the same process as, another specified entity.
-
E.
lighthouseMaintainedBy
Indicates that a lighthouse is operated, serviced, or kept in working condition by a particular person, organization, or authority.
- 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e675de35188190840dc7d04c1d5fd9 |
completed | April 20, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:42 p.m.