Triple
T8482468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Go |
E200551
|
entity |
| Predicate | endgamePhaseName |
P75603
|
FINISHED |
| Object | yose |
—
|
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: yose | Statement: [Go, endgamePhaseName, yose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endgamePhaseName Context triple: [Go, endgamePhaseName, yose]
-
A.
finalPhaseOf
Indicates that one process, stage, or event constitutes the concluding or last phase of another broader process or sequence.
-
B.
codeNameOfPhase
Indicates that an entity is assigned a specific code name corresponding to a particular phase in a process or lifecycle.
-
C.
hasPhaseOfPlay
chosen
Indicates a relationship where a broader game or activity includes or is associated with a specific phase or segment of play.
-
D.
finalMissionPhase
Indicates that an entity is in, or corresponds to, the concluding or last phase of a mission.
-
E.
clinchingGameState
Indicates a game state in which one side can secure a series, title, or advancement with a win (or, less commonly, face elimination with a loss).
- 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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53638c48190b742fc51d1b4442a |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:12 p.m.