Triple
T28269415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 蔣 |
E712801
|
entity |
| Predicate | associatedDynastyOrEra |
P7426
|
FINISHED |
| Object | Republic of China political leaders |
—
|
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: Republic of China political leaders | Statement: [蔣, associatedDynastyOrEra, Republic of China political leaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDynastyOrEra Context triple: [蔣, associatedDynastyOrEra, Republic of China political leaders]
-
A.
dynasticEraName
Indicates the named historical period or era associated with a particular dynasty’s rule.
-
B.
associatedWithDynasty
chosen
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
-
C.
dynastyAlsoKnownAs
Indicates that a dynasty is referred to by an alternative name, alias, or variant designation.
-
D.
dynastyServed
Indicates that a person or group rendered service or allegiance to a particular ruling dynasty.
-
E.
associatedWithDynastyFoundation
Indicates a relationship in which an entity is connected to the founding or establishment of a particular dynasty.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_6a01185c46f0819089b4a2ad3c3e2f33 |
completed | May 10, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_6a0117e19e008190870663dd45084416 |
completed | May 10, 2026, 11:42 p.m. |
Created at: April 27, 2026, 11:16 p.m.