Triple
T29358292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: Edge of Extinction |
E744507
|
entity |
| Predicate | includesReturningPlayers |
P200960
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Survivor: Edge of Extinction, includesReturningPlayers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesReturningPlayers Context triple: [Survivor: Edge of Extinction, includesReturningPlayers, true]
-
A.
includesActivePlayers
Indicates that a group, list, or collection contains one or more players who are currently active.
-
B.
includesPositionPlayers
Indicates that a group, team, or lineup contains players assigned to specific positions.
-
C.
hasRetiredPlayersFrom
Indicates that an entity has players who previously played for it and have since retired, originating from the specified source entity (e.g., team, league, or country).
-
D.
eligiblePlayersFrom
Indicates that a set of players qualifies to be selected from a particular source, context, or group based on defined eligibility criteria.
-
E.
supportsPlayers
Indicates that an entity provides compatibility or functionality for one or more players to participate or be used.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69ffbe9e47688190a2692566dc326646 |
completed | May 9, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69ffbb7b45388190b62cbde5c2d435cd |
completed | May 9, 2026, 10:55 p.m. |
| PDg | Predicate description generation | batch_69ffbe9c7c348190b6b72455d6a3e3d8 |
completed | May 9, 2026, 11:09 p.m. |
Created at: April 28, 2026, 2:14 p.m.