Triple
T37457083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secret Mage |
E930825
|
entity |
| Predicate | gameplanMid |
P29774
|
FINISHED |
| Object | leverage Secret synergies for tempo swings |
—
|
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: leverage Secret synergies for tempo swings | Statement: [Secret Mage, gameplanMid, leverage Secret synergies for tempo swings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameplanMid Context triple: [Secret Mage, gameplanMid, leverage Secret synergies for tempo swings]
-
A.
postGamesPlan
Indicates that an entity publishes or shares a plan or strategy related to games after they have concluded.
-
B.
masterplannedBy
Indicates that an area or development project has been comprehensively designed or organized according to an overarching plan created by a specific planner or planning entity.
-
C.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
D.
platformPlanned
Indicates that a platform is intended or scheduled to be created, implemented, or made available in the future.
-
E.
partOfPlan
chosen
Indicates that one entity is included as a component or step within a broader plan or strategy.
- 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_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.