Triple
T24144446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belle Tout Lighthouse |
E598336
|
entity |
| Predicate | operatorUntilDecommissioning |
P155005
|
FINISHED |
| Object | Trinity House |
—
|
NE NERFINISHED |
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: Trinity House | Statement: [Belle Tout Lighthouse, operatorUntilDecommissioning, Trinity House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorUntilDecommissioning Context triple: [Belle Tout Lighthouse, operatorUntilDecommissioning, Trinity House]
-
A.
estimatedDecommissioningDuration
Indicates the expected length of time required to complete the decommissioning process of an entity.
-
B.
decommissioningStatus
Indicates the current phase or condition of an entity in the process of being taken out of active service or use.
-
C.
decommissionedBy
Indicates that an entity was formally taken out of service or use by a specific agent or authority.
-
D.
decommissioningActivity
Indicates the process or actions involved in taking something out of service, shutting it down, or formally retiring it from use.
-
E.
decommissioningEndDate
Indicates the date on which a decommissioning process or status for something is completed or officially ends.
- 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e008efbc8190ac6c12d3ba5dd5d8 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 11:29 p.m.