Triple
T35654632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Constabulary |
E1030250
|
entity |
| Predicate | ceasedToExistAsLegalEntityOn |
P81396
|
FINISHED |
| Object | 1 April 2013 |
—
|
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: 1 April 2013 | Statement: [Northern Constabulary, ceasedToExistAsLegalEntityOn, 1 April 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasedToExistAsLegalEntityOn Context triple: [Northern Constabulary, ceasedToExistAsLegalEntityOn, 1 April 2013]
-
A.
ceaseToExistDecisionDate
Indicates the date on which a formal decision was made that something will cease to exist or be terminated.
-
B.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
-
C.
hasDissolutionDate
chosen
Indicates the date on which an entity, such as an organization or legal arrangement, formally ceases to exist or is officially dissolved.
-
D.
deJureRemovalDate
Indicates the official, legally recognized date on which an entity is formally removed from a position, status, or record.
-
E.
cessationDate
Indicates the date on which an ongoing state, activity, or relationship 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f769dec81908e0e638851ac83dd |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.