Triple
T1737512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor |
E37951
|
entity |
| Predicate | franchiseDebutYear |
P7549
|
FINISHED |
| Object | 1997 (original Expedition Robinson format) |
—
|
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: 1997 (original Expedition Robinson format) | Statement: [Survivor, franchiseDebutYear, 1997 (original Expedition Robinson format)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: franchiseDebutYear Context triple: [Survivor, franchiseDebutYear, 1997 (original Expedition Robinson format)]
-
A.
franchiseStartSeason
Indicates the season in which a particular franchise or series first began or was introduced.
-
B.
franchiseStart
Indicates the point in time or event at which a franchise or franchising relationship is initiated or begins.
-
C.
debutYear
chosen
Indicates the year in which an entity first appeared, was introduced, or made its initial public debut.
-
D.
officialOpeningYear
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
E.
firstRunningYear
Indicates the year in which something (such as an event, service, or operation) first began running or was initially active.
- 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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.