Triple
T29358295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: Edge of Extinction |
E744507
|
entity |
| Predicate | numberOfReturningPlayers |
P200960
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Survivor: Edge of Extinction, numberOfReturningPlayers, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfReturningPlayers Context triple: [Survivor: Edge of Extinction, numberOfReturningPlayers, 4]
-
A.
includesReturningPlayers
chosen
Indicates that a group, event, or context contains participants who have taken part previously and are now returning.
-
B.
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).
-
C.
managedPlayers
Indicates that one entity has managerial responsibility or authority over the players represented by the other entity.
-
D.
hasPlayerCount
Indicates the number of players associated with or participating in a given entity or activity.
-
E.
hasReturnedToPlayIn
Indicates that an entity has resumed participating or performing in a particular event, context, or location after a period of absence.
- 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_69ffef812da48190b875a7376b24f92d |
completed | May 10, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69ffedecd580819097851b1473fdd6ed |
completed | May 10, 2026, 2:31 a.m. |
Created at: April 28, 2026, 2:14 p.m.