Triple
T29358293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: Edge of Extinction |
E744507
|
entity |
| Predicate | includesNewPlayers |
P197408
|
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, includesNewPlayers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesNewPlayers Context triple: [Survivor: Edge of Extinction, includesNewPlayers, true]
-
A.
featuresNewPlayers
chosen
Indicates that something includes or highlights individuals who are new participants or recently added players.
-
B.
includesReturningPlayers
Indicates that a group, event, or context contains participants who have taken part previously and are now returning.
-
C.
hasPlayerWhoLaterJoined
Indicates that an entity has a player associated with it who, at some later time, joined another specified entity or group.
-
D.
emergingPlayer
Indicates that an entity is a player who is newly gaining prominence, skill, or recognition within a particular context or domain.
-
E.
supportsPlayers
Indicates that an entity provides compatibility or functionality for one or more players to participate or be used.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69ffbf84f4948190b41a7bba07ae61ec |
completed | May 9, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69ffbf0a59f88190870dbe25d8a63a00 |
completed | May 9, 2026, 11:11 p.m. |
Created at: April 28, 2026, 2:14 p.m.