Triple

T28954467
Position Surface form Disambiguated ID Type / Status
Subject Survivor: San Juan del Sur E731115 entity
Predicate finalTribalCouncilVote P10095 FINISHED
Object Natalie Anderson defeated Jaclyn Schultz and Missy Payne 5–2–1 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: Natalie Anderson defeated Jaclyn Schultz and Missy Payne 5–2–1 | Statement: [Survivor: San Juan del Sur, finalTribalCouncilVote, Natalie Anderson defeated Jaclyn Schultz and Missy Payne 5–2–1]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: finalTribalCouncilVote
Context triple: [Survivor: San Juan del Sur, finalTribalCouncilVote, Natalie Anderson defeated Jaclyn Schultz and Missy Payne 5–2–1]
  • A. hasTribalCouncil
    Indicates that an entity is associated with or governed by a specific tribal council.
  • B. voteResult chosen
    Indicates the outcome or decision produced by a voting process involving the related entities.
  • C. finalHeld
    Indicates that an entity ultimately retains possession or control of another entity at the conclusion of a process or event.
  • D. councilOutcome
    Indicates the result or decision produced by a council after its deliberation or proceedings.
  • E. heldCouncil
    Indicates that an entity organized and conducted a formal meeting or assembly for discussion or decision-making with other participants.
  • 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_69fba2877b248190a974eb092243c0c4 completed May 6, 2026, 8:20 p.m.
PD Predicate disambiguation batch_69fb8d06a1b48190a937aa410d159dfa completed May 6, 2026, 6:48 p.m.
Created at: April 28, 2026, 8:46 a.m.