Triple
T32059996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Crystal Maze (revival) |
E818720
|
entity |
| Predicate | endGame |
P159759
|
FINISHED |
| Object | Crystal Dome token collection |
—
|
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: Crystal Dome token collection | Statement: [The Crystal Maze (revival), endGame, Crystal Dome token collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endGame Context triple: [The Crystal Maze (revival), endGame, Crystal Dome token collection]
-
A.
hasGameEndCondition
chosen
Indicates that an entity specifies the condition or set of conditions under which a game is considered finished or concluded.
-
B.
gameOutcome
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
-
C.
decidingGameLoser
Indicates that the referenced entity is the loser in the decisive or final game that determines the overall outcome of a series or competition.
-
D.
endedPlay
Indicates that an entity has brought a play, performance, or game to a conclusion.
-
E.
ElamEnding
Indicates that an entity marks the end or termination of something related to Elam (e.g., an Elam-related period, event, or process).
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4f42ea08190a04fb569e8858ddc |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:21 a.m.