Triple
T26323889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Đinh Phế Đế |
E662191
|
entity |
| Predicate | conflictDuringReign |
P98782
|
FINISHED |
| Object | court power struggles |
—
|
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: court power struggles | Statement: [Đinh Phế Đế, conflictDuringReign, court power struggles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictDuringReign Context triple: [Đinh Phế Đế, conflictDuringReign, court power struggles]
-
A.
conflictTypeDuringReign
chosen
Indicates the type or category of conflict that occurred during a particular ruler’s reign.
-
B.
reignDuringConflict
Indicates that a ruler’s period of reign overlaps in time with a specified conflict or war.
-
C.
sultanDuringConflict
Indicates that an individual holds the position or role of sultan during a specific conflict or period of armed struggle.
-
D.
successionConflict
Indicates a dispute or struggle over who has the legitimate right to succeed to a position, title, or authority.
-
E.
facedConflictOver
Indicates that two or more entities experienced opposition, dispute, or tension concerning a particular issue, resource, or situation.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 10:29 p.m.