Triple
T37665914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cascade Kingdom |
E937818
|
entity |
| Predicate | precedesInGame |
P160842
|
FINISHED |
| Object | Sand Kingdom |
—
|
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: Sand Kingdom | Statement: [Cascade Kingdom, precedesInGame, Sand Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesInGame Context triple: [Cascade Kingdom, precedesInGame, Sand Kingdom]
-
A.
precedesInFranchise
Indicates that one installment in a franchise comes before another in the franchise’s canonical or release order.
-
B.
precedesInUniverse
chosen
Indicates that one event or entity occurs earlier than another within the timeline or causal order of a given fictional or conceptual universe.
-
C.
precedesInFilm
Indicates that one film is released or occurs earlier in sequence or narrative order than another film.
-
D.
playInGameIntroduced
Indicates that an entity participates as a playable element within the specific game in which it was first introduced.
-
E.
precededInTournamentSequence
Indicates that one participant or event occurred earlier than another in the ordered sequence of a tournament.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: May 3, 2026, 4:18 p.m.