Triple
T8093831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bai Qi |
E188933
|
entity |
| Predicate | victories |
P75969
|
FINISHED |
| Object | multiple major campaigns against rival states |
—
|
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: multiple major campaigns against rival states | Statement: [Bai Qi, victories, multiple major campaigns against rival states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victories Context triple: [Bai Qi, victories, multiple major campaigns against rival states]
-
A.
victoryIn
Indicates that one entity achieves a win or success in a specific contest, event, or competitive context involving another entity.
-
B.
typeOfVictory
Indicates the specific manner or category in which a victory was achieved.
-
C.
victoryTarget
Indicates that one entity is the intended opponent, objective, or condition that must be overcome or achieved for the other entity to attain victory.
-
D.
winsDefinition
chosen
Indicates that one entity achieves victory or success over another in a contest, competition, or conflict.
-
E.
defeat
Indicates that one entity wins against and overcomes another in a contest, conflict, or competition.
- 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.