Triple
T28569043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: Guatemala |
E722762
|
entity |
| Predicate | featuresReturningPlayers |
P197389
|
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: Guatemala, featuresReturningPlayers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresReturningPlayers Context triple: [Survivor: Guatemala, featuresReturningPlayers, true]
-
A.
featuresPlayers
Indicates that something includes or showcases one or more players as part of its content or composition.
-
B.
featuresPlayer
Indicates that something includes or prominently presents a particular player as part of its content or composition.
-
C.
featuresPlayersFrom
Indicates that something (such as a work, event, or production) includes or showcases players originating from a specified source, group, or location.
-
D.
featuresTopPlayersFrom
Indicates that something includes or showcases the most prominent or best-performing players from a specified source or group.
-
E.
featuresTopPlayers
Indicates that something prominently presents or showcases the most outstanding or highly ranked players.
- 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
| PDg | Predicate description generation | batch_69fe8f730bb88190975bffd49f5e0f3b |
completed | May 9, 2026, 1:35 a.m. |
Created at: April 28, 2026, 4:08 a.m.