Triple
T37457550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tempo Rogue |
E930836
|
entity |
| Predicate | gamePhaseStrength |
P112976
|
FINISHED |
| Object | early game |
—
|
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: early game | Statement: [Tempo Rogue, gamePhaseStrength, early game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gamePhaseStrength Context triple: [Tempo Rogue, gamePhaseStrength, early game]
-
A.
hasPhaseOfPlay
Indicates a relationship where a broader game or activity includes or is associated with a specific phase or segment of play.
-
B.
commonRacePhase
Indicates that two or more race events share the same phase or stage within a larger racing sequence or structure.
-
C.
typeOfPlayStrength
chosen
Indicates the relative intensity or power level with which a play or move is executed or characterized.
-
D.
bossPhaseCount
Indicates the number of distinct phases or stages that a boss encounter progresses through.
-
E.
movementPhase
Indicates the specific stage or step within a larger movement or motion process that an action or entity is currently in.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.