Triple
T33678825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ugeumchi |
E862835
|
entity |
| Predicate | peasantForcesCharacteristic |
P60742
|
FINISHED |
| Object | poorly armed |
—
|
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: poorly armed | Statement: [Battle of Ugeumchi, peasantForcesCharacteristic, poorly armed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peasantForcesCharacteristic Context triple: [Battle of Ugeumchi, peasantForcesCharacteristic, poorly armed]
-
A.
factionCharacteristic
Indicates that a particular characteristic, trait, or property is associated with or defines a given faction.
-
B.
opponentForceCharacteristic
chosen
Indicates a characteristic or attribute that describes the nature, capability, or condition of an opposing force.
-
C.
royalistForcesCharacteristic
Indicates that a characteristic, trait, or attribute is associated specifically with royalist forces.
-
D.
battleCharacteristic
Indicates a relationship where a specific trait, quality, or feature is attributed to a battle or combat scenario.
-
E.
militaryCharacteristic
Indicates that one entity possesses a specific military-related attribute, quality, or feature in relation to another entity or context.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fa5cd5988190800ed6d7ab981175 |
completed | May 3, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:43 a.m.