Triple
T29126680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: David vs. Goliath |
E738247
|
entity |
| Predicate | locationUsedInSeason |
P4415
|
FINISHED |
| Object | Fiji |
—
|
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: Fiji | Statement: [Survivor: David vs. Goliath, locationUsedInSeason, Fiji]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationUsedInSeason Context triple: [Survivor: David vs. Goliath, locationUsedInSeason, Fiji]
-
A.
usedInSeason
chosen
Indicates that something (such as an item, strategy, or element) is utilized or appears within a particular season.
-
B.
subsequentSeasonLocationsInclude
Indicates that the locations specified are among those used in one or more seasons that follow a given season in a series or sequence.
-
C.
primarySeasonLocation
Indicates the main geographic location where an entity’s primary season, activity period, or operations take place.
-
D.
hostedInSeason
Indicates that an event, show, or activity took place or was held during a specific season.
-
E.
occurredInSeason
Indicates that an event or occurrence took place during a specific season within a temporal sequence (such as a TV show season or sports season).
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69ffff262fac8190a26ed0577e1860bd |
completed | May 10, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69fffcad7d7c8190a4ad7bb35e33bb75 |
completed | May 10, 2026, 3:34 a.m. |
Created at: April 28, 2026, 11:29 a.m.