Triple
T37457145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Spell Mage |
E930827
|
entity |
| Predicate | typicalGamePlan |
P207638
|
FINISHED |
| Object | stall 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: stall early game | Statement: [Big Spell Mage, typicalGamePlan, stall early game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGamePlan Context triple: [Big Spell Mage, typicalGamePlan, stall early game]
-
A.
typicalGame
Indicates a relationship where one entity is characterized as a standard, representative, or commonly occurring example of a game for the other entity or context.
-
B.
typicalGamePurpose
Indicates the usual or primary purpose for which a game is designed or typically played.
-
C.
typicalPlanForBlack
Indicates the standard or commonly used strategic plan or sequence of moves employed by the black side in a given game or scenario.
-
D.
typicalOutcomeOfPlaying
Indicates the usual result or consequence that tends to occur when an activity or game is played.
-
E.
typicalMove
Indicates that an entity commonly or characteristically performs a particular movement or action.
- F. None of above. chosen
Provenance (4 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_6a038156e0288190bc1f2efe9d7f2646 |
completed | May 12, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_6a038094212881909d8f451fee75b2a2 |
completed | May 12, 2026, 7:33 p.m. |
| PDg | Predicate description generation | batch_6a0381561778819081a6873af4f006d3 |
completed | May 12, 2026, 7:36 p.m. |
Created at: May 3, 2026, 4:17 p.m.