Triple
T26029879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hưng Thống |
E647398
|
entity |
| Predicate | predecessorEraDynasty |
P46282
|
FINISHED |
| Object | Đinh dynasty |
—
|
NE NERFINISHED |
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: Đinh dynasty | Statement: [Hưng Thống, predecessorEraDynasty, Đinh dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorEraDynasty Context triple: [Hưng Thống, predecessorEraDynasty, Đinh dynasty]
-
A.
historicalEntityPredecessor
Indicates that one historical entity existed or held a role before another, serving as its predecessor in time or sequence.
-
B.
predecessorDynasticSituation
Indicates that one dynastic situation directly precedes another in a historical or genealogical sequence.
-
C.
predecessorAsEasternRuler
Indicates that one entity previously held the position of eastern ruler before another entity assumed that same role.
-
D.
earlierDynasty
chosen
Indicates that one dynasty chronologically precedes another in historical succession.
-
E.
predecessorAsSupremeRuler
Indicates that one entity previously held the position of supreme ruler immediately before another 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 22, 2026, 9:06 a.m.