Triple
T28954387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: Palau |
E731113
|
entity |
| Predicate | openingLocationSequence |
P54492
|
FINISHED |
| Object | World War II shipwrecks in Palau |
—
|
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: World War II shipwrecks in Palau | Statement: [Survivor: Palau, openingLocationSequence, World War II shipwrecks in Palau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingLocationSequence Context triple: [Survivor: Palau, openingLocationSequence, World War II shipwrecks in Palau]
-
A.
openingSequenceType
Indicates the specific kind or category of an opening sequence associated with an entity or event.
-
B.
hasOpeningSequenceLocation
chosen
Indicates the specific location where the opening sequence of something (such as a film, show, or event) takes place.
-
C.
openingSequenceWorkPerformed
Indicates that a specific work is performed as the opening sequence of a larger performance or program.
-
D.
openingSequence
Indicates the initial ordered set of actions or events that begin a process, performance, or interaction.
-
E.
openingSequenceFormat
Indicates the specific structural or stylistic format used for an opening sequence in a work or presentation.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 8:46 a.m.