Triple
T28954523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: Worlds Apart |
E731116
|
entity |
| Predicate | finalTribalCouncilFormat |
P111445
|
FINISHED |
| Object | Final three |
—
|
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: Final three | Statement: [Survivor: Worlds Apart, finalTribalCouncilFormat, Final three]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalTribalCouncilFormat Context triple: [Survivor: Worlds Apart, finalTribalCouncilFormat, Final three]
-
A.
hasTribalCouncil
Indicates that an entity is associated with or governed by a specific tribal council.
-
B.
typicalFinalFormat
chosen
Indicates that something represents the usual or standard structure or arrangement in which an item, document, or data is ultimately presented or delivered.
-
C.
finalHeld
Indicates that an entity ultimately retains possession or control of another entity at the conclusion of a process or event.
-
D.
grandFinal
Indicates a culminating, decisive final event or match that determines the ultimate outcome or champion in a competition or series.
-
E.
semiFinalFormat
Indicates the structure or rules used to organize and play the semifinal stage of a competition or tournament.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 28, 2026, 8:46 a.m.