Triple
T16126728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taikazan |
E391290
|
entity |
| Predicate | gamePhase |
P75603
|
FINISHED |
| Object | used throughout match duration |
—
|
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: used throughout match duration | Statement: [Taikazan, gamePhase, used throughout match duration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gamePhase Context triple: [Taikazan, gamePhase, used throughout match duration]
-
A.
hasPhaseOfPlay
chosen
Indicates a relationship where a broader game or activity includes or is associated with a specific phase or segment of play.
-
B.
gameState
Indicates the current status or condition of a game at a particular point in time, including relevant rules, progress, and contextual information.
-
C.
movementPhase
Indicates the specific stage or step within a larger movement or motion process that an action or entity is currently in.
-
D.
currentMissionPhase
Indicates the specific phase or stage that a mission is presently in within its overall lifecycle.
-
E.
programPhase
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20204fb408190b58d49d0d64bb740 |
completed | April 17, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.