Triple
T8093828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bai Qi |
E188933
|
entity |
| Predicate | strategicStyle |
P31887
|
FINISHED |
| Object | decisive annihilation of enemy forces |
—
|
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: decisive annihilation of enemy forces | Statement: [Bai Qi, strategicStyle, decisive annihilation of enemy forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicStyle Context triple: [Bai Qi, strategicStyle, decisive annihilation of enemy forces]
-
A.
strategicStance
Indicates the overarching strategic position, approach, or orientation an entity adopts in relation to others or to a particular situation.
-
B.
strategyType
chosen
Indicates the specific kind or category of strategy associated with an entity or action.
-
C.
tacticalStyle
Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
-
D.
styleOfPlay
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
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.
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_69ca82b7b3e88190b9041ab0ef28b3cb |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4222b68c81909c8bc326763240d0 |
completed | March 31, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:30 p.m.