Triple
T28569054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: Guatemala |
E722762
|
entity |
| Predicate | hasContestant |
P46216
|
FINISHED |
| Object | Rafe Judkins |
—
|
NE NERFINISHED |
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: Rafe Judkins | Statement: [Survivor: Guatemala, hasContestant, Rafe Judkins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContestant Context triple: [Survivor: Guatemala, hasContestant, Rafe Judkins]
-
A.
hasNotableContestant
Indicates that an entity (such as a competition, show, or event) includes or is associated with a contestant who is notable or distinguished in some way.
-
B.
contestantOn
chosen
Indicates that one entity participates as a competitor in a contest, show, or competition associated with another entity.
-
C.
featuresContestantsFrom
Indicates that something, typically a show or event, includes contestants originating from a specified source or group.
-
D.
belongsToContest
Indicates that an entity is a participant in, or is associated as an entry with, a specific contest.
-
E.
contestantActivity
Indicates that a contestant engages in or performs a particular activity within a competition or contest context.
- 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69ffc605b0648190a7abe9128b0d857a |
completed | May 9, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69ffc5742d80819099f947ece78d5700 |
completed | May 9, 2026, 11:38 p.m. |
Created at: April 28, 2026, 4:08 a.m.