Triple
T8703377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guominjun |
E206586
|
entity |
| Predicate | governmentTypeInControlledAreas |
P84635
|
FINISHED |
| Object | military government |
—
|
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: military government | Statement: [Guominjun, governmentTypeInControlledAreas, military government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentTypeInControlledAreas Context triple: [Guominjun, governmentTypeInControlledAreas, military government]
-
A.
militaryControl
Indicates that one entity exercises authoritative military power, command, or occupation over another entity or territory.
-
B.
governmentTypeStrengthened
Indicates that the form or structure of a government has been reinforced, consolidated, or made more powerful or stable relative to its previous state.
-
C.
capitalControlled
Indicates that one entity exercises control or decisive influence over the capital or financial resources of another entity.
-
D.
townControlled
Indicates that one entity has governing authority or administrative control over a town.
-
E.
governedIn
Indicates that one entity exercised governing authority or administrative control within a specified place or jurisdiction.
- F. None of above. chosen
Provenance (4 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_69ca835645e881908f00e3c8b51da81d |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58fa0a208190a520e0e1f7faaea9 |
completed | March 31, 2026, 11:30 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc582412f48190ae819965bfb0e75d |
completed | March 31, 2026, 11:26 p.m. |
Created at: March 30, 2026, 6:34 p.m.