Triple
T28690252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: One World |
E729256
|
entity |
| Predicate | filmedBackToBackWith |
P35866
|
FINISHED |
| Object | Survivor: South Pacific |
—
|
NE NERFINISHED |
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: Survivor: South Pacific | Statement: [Survivor: One World, filmedBackToBackWith, Survivor: South Pacific]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filmedBackToBackWith Context triple: [Survivor: One World, filmedBackToBackWith, Survivor: South Pacific]
-
A.
hasSequelShotBackToBackWith
chosen
Indicates that two sequels were filmed consecutively or simultaneously as part of the same production schedule.
-
B.
filmedBefore
Indicates that one filming event occurred earlier in time than another filming event.
-
C.
followedByInFilm
Indicates that one scene, shot, or event in a film immediately succeeds another in the narrative or editing sequence.
-
D.
filmedAs
Indicates that an entity was recorded or captured in a particular form, version, or role during a filming or production process.
-
E.
filmedFor
Indicates that something was recorded or produced specifically for a particular purpose, audience, platform, or project.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65684223c8190867c123acf504527 |
completed | May 2, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:35 a.m.