Triple
T517010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russo-Japanese War |
E10730
|
entity |
| Predicate | combatantType |
P7256
|
FINISHED |
| Object | industrialized nation-states |
—
|
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: industrialized nation-states | Statement: [Russo-Japanese War, combatantType, industrialized nation-states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantType Context triple: [Russo-Japanese War, combatantType, industrialized nation-states]
-
A.
warfareType
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
B.
combatantStrength
Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
-
C.
usedWarfareType
Indicates the specific type or method of warfare that an entity employed in a conflict or military context.
-
D.
typeOfTroops
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
E.
militaryCharacteristic
chosen
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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f184c3a481909bf60bb627b0ea88 |
completed | Feb. 28, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69a2f0151e8c81909a82b58ac0515eba |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.