Triple
T13494340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heiji Rebellion |
E320719
|
entity |
| Predicate | militaryConflictType |
P1403
|
FINISHED |
| Object | succession and power struggle |
—
|
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: succession and power struggle | Statement: [Heiji Rebellion, militaryConflictType, succession and power struggle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryConflictType Context triple: [Heiji Rebellion, militaryConflictType, succession and power struggle]
-
A.
warfareType
chosen
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
B.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
C.
militaryConflictIn
Indicates that a military conflict takes place within, or is geographically located in, a specified area or region.
-
D.
militaryConflictView
Indicates a perspective, interpretation, or representation of a specific military conflict or battle.
-
E.
opposedWarfareType
Indicates that one entity is in opposition to, or acts against, the type or form of warfare represented by the other entity.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf4da2c88190a867b53529d39545 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.