Triple
T29488768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: Cambodia |
E748009
|
entity |
| Predicate | castingConcept |
P166964
|
FINISHED |
| Object | returning players |
—
|
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: returning players | Statement: [Survivor: Cambodia, castingConcept, returning players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: castingConcept Context triple: [Survivor: Cambodia, castingConcept, returning players]
-
A.
cast
Indicates that an agent selects and assigns a person or thing to play a specific role or function in a production or context.
-
B.
castingReason
Indicates the reason or justification for selecting or assigning a particular entity (e.g., a person or object) to a specific role, function, or category.
-
C.
castBy
Indicates that one entity (typically a role or character) is portrayed or performed by another entity (typically an actor or performer).
-
D.
castIn
Indicates that an actor or performer appears in a particular film, show, or production.
-
E.
castingNote
Indicates that there is an explanatory note or comment about how a role was cast or performed in a production.
- 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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c08d734819088f227ef5b054acb |
completed | May 2, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6642e676c8190af0e6b1416eed6d2 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 4:11 p.m.