Triple
T30026733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Competition Commission |
E762899
|
entity |
| Predicate | dissolvedOnDate |
P81396
|
FINISHED |
| Object | 2014-04-01 |
—
|
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: 2014-04-01 | Statement: [Competition Commission, dissolvedOnDate, 2014-04-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissolvedOnDate Context triple: [Competition Commission, dissolvedOnDate, 2014-04-01]
-
A.
dissolvedWhen
Indicates that one entity ceases to exist, function, or remain intact at the time or under the conditions specified by another entity or event.
-
B.
dissolvedOnOrAround
Indicates that an entity ceased to exist, function, or remain in force on or approximately around a specified date.
-
C.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
-
D.
hasDissolutionDate
chosen
Indicates the date on which an entity, such as an organization or legal arrangement, formally ceases to exist or is officially dissolved.
-
E.
dissolvedBefore
Indicates that one entity ceased to exist, function, or remain in solution at an earlier time than another entity.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 6:48 p.m.