Triple
T17809945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Yun |
E444670
|
entity |
| Predicate | governmentSystemUnderRule |
P125963
|
FINISHED |
| Object | warlord regime in Yunnan |
—
|
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: warlord regime in Yunnan | Statement: [Long Yun, governmentSystemUnderRule, warlord regime in Yunnan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentSystemUnderRule Context triple: [Long Yun, governmentSystemUnderRule, warlord regime in Yunnan]
-
A.
politicalSystemDuringRule
Indicates the type of political system that was in place during a particular ruler’s period of governance.
-
B.
laterPoliticalSystemUnderRule
Indicates that one political system came under the rule or authority of another political system at a later point in time.
-
C.
countryGovernmentSystemDuringExistence
Indicates the form of government a country had during its period of existence.
-
D.
نظامالحكم
chosen
Indicates the type or structure of governance or political system under which an entity is ruled.
-
E.
ruledUnderPolity
Indicates that an entity exercised rule or governance while being subordinate to, or within the authority framework of, a particular polity.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4887a50488190b9c148146ec607e6 |
completed | April 19, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:14 a.m.