Triple
T28954486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: San Juan del Sur |
E731115
|
entity |
| Predicate | hasNotableContestant |
P199906
|
FINISHED |
| Object | Natalie Anderson |
—
|
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: Natalie Anderson | Statement: [Survivor: San Juan del Sur, hasNotableContestant, Natalie Anderson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableContestant Context triple: [Survivor: San Juan del Sur, hasNotableContestant, Natalie Anderson]
-
A.
hasNotableContender
Indicates that an entity has a significant rival, challenger, or competitor recognized as noteworthy in relation to it.
-
B.
notableContestantType
Indicates that an entity is a notable or distinguished example of a particular type or category of contestant.
-
C.
hasNotablePerformer
Indicates that an entity features or is associated with a performer who is particularly prominent, famous, or otherwise noteworthy.
-
D.
hasNotableSpeaker
Indicates that an event, gathering, or occasion features a speaker who is distinguished or noteworthy in some significant way.
-
E.
hasNotableRace
Indicates that an entity is associated with a race or competition that is considered notable or significant.
- F. None of above. chosen
Provenance (4 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_69ff63e6b61081909c648bf0ff279481 |
completed | May 9, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ff6381867881908ae0545df4b71df5 |
completed | May 9, 2026, 4:40 p.m. |
| PDg | Predicate description generation | batch_69ff63e5c35081908f69ac44e12b8f52 |
completed | May 9, 2026, 4:42 p.m. |
Created at: April 28, 2026, 8:46 a.m.