Triple
T29871646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mii Contest Channel |
E758607
|
entity |
| Predicate | serviceTerminationDate |
P101820
|
FINISHED |
| Object | 2013-06-28 |
—
|
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: 2013-06-28 | Statement: [Mii Contest Channel, serviceTerminationDate, 2013-06-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceTerminationDate Context triple: [Mii Contest Channel, serviceTerminationDate, 2013-06-28]
-
A.
cessationDate
chosen
Indicates the date on which an ongoing state, activity, or relationship comes to an end.
-
B.
holderEndDate
Indicates the date on which an entity’s role as holder of something (e.g., an asset, position, or right) comes to an end.
-
C.
decommissioningEndDate
Indicates the date on which a decommissioning process or status for something is completed or officially ends.
-
D.
serviceModuleJettisonDate
Indicates the date on which a service module is detached or jettisoned from the main vehicle or system.
-
E.
setsTermEndDateFor
Indicates setting or assigning the end date of a term or period for 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 29, 2026, 5:53 p.m.