Triple
T15466113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crazy Eight |
E372033
|
entity |
| Predicate | strategyNote |
P118338
|
FINISHED |
| Object | can provide both offense and defense simultaneously |
—
|
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: can provide both offense and defense simultaneously | Statement: [Crazy Eight, strategyNote, can provide both offense and defense simultaneously]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategyNote Context triple: [Crazy Eight, strategyNote, can provide both offense and defense simultaneously]
-
A.
strategyType
Indicates the specific kind or category of strategy associated with an entity or action.
-
B.
strategyEmphasis
Indicates an entity’s primary focus or priority within a broader strategy or plan.
-
C.
structureNote
Indicates a note or annotation that describes or clarifies the structure, organization, or arrangement of something.
-
D.
strategyComponent
Indicates that one element functions as a constituent or building block within a broader strategy.
-
E.
strategicPrinciple
Indicates that one entity embodies, expresses, or is governed by a guiding strategic principle in relation to another entity or context.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f680cec8190836a5ec841dee224 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded5deee00819099fa3e43313312e1 |
completed | April 15, 2026, 12:03 a.m. |
Created at: April 10, 2026, 3:33 a.m.