Triple
T1016490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planet Earth II |
E21940
|
entity |
| Predicate | originalRunEndDate |
P6603
|
FINISHED |
| Object | 2016-12-11 |
—
|
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: 2016-12-11 | Statement: [Planet Earth II, originalRunEndDate, 2016-12-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalRunEndDate Context triple: [Planet Earth II, originalRunEndDate, 2016-12-11]
-
A.
originalRunEra
Indicates the time period or era during which something (such as a show, series, or product) was first originally run or released.
-
B.
serializationEndYear
Indicates the year in which the serialization or serialized publication of an entity concluded.
-
C.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
D.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
E.
operatedUntil
chosen
Indicates that an entity continued to function or be in operation up to a specified end time or date.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c1e9d08190baf7e81f3777168d |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b7238d4c8190b22d6c2ac0ac4911 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.