Triple
T32834102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Government |
E839775
|
entity |
| Predicate | dominantMilitaryForce |
P104865
|
FINISHED |
| Object | Beiyang Army |
—
|
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: Beiyang Army | Statement: [Northern Government, dominantMilitaryForce, Beiyang Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantMilitaryForce Context triple: [Northern Government, dominantMilitaryForce, Beiyang Army]
-
A.
hasArmedForces
chosen
Indicates that an entity possesses or maintains organized military forces under its control.
-
B.
stateOfForces
Indicates the condition, disposition, or readiness level of military or organizational forces at a given time.
-
C.
militaryOrganization
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
-
D.
forzaBelligerante
Indicates a party’s status or role as a belligerent force engaged in a conflict or war.
-
E.
armedForcesCategory
Indicates the classification of a country's or group's military forces into a specific type or category (e.g., army, navy, air force, paramilitary).
- 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 1, 2026, 1:16 a.m.