Triple
T37457082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secret Mage |
E930825
|
entity |
| Predicate | gameplanEarly |
P14398
|
FINISHED |
| Object | establish board and play cheap Secrets |
—
|
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: establish board and play cheap Secrets | Statement: [Secret Mage, gameplanEarly, establish board and play cheap Secrets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameplanEarly Context triple: [Secret Mage, gameplanEarly, establish board and play cheap Secrets]
-
A.
postGamesPlan
Indicates that an entity publishes or shares a plan or strategy related to games after they have concluded.
-
B.
plan
chosen
Indicates that an entity intends or arranges for a future action or sequence of actions to occur.
-
C.
partOfPlan
Indicates that one entity is included as a component or step within a broader plan or strategy.
-
D.
originalPlan
Indicates that one entity is the initial or primary plan or intended course of action associated with another entity.
-
E.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
- 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_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.