Triple
T28313371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caucasus front of the Crimean War |
E714062
|
entity |
| Predicate | hasSecondaryBelligerent |
P180603
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [Caucasus front of the Crimean War, hasSecondaryBelligerent, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryBelligerent Context triple: [Caucasus front of the Crimean War, hasSecondaryBelligerent, United Kingdom]
-
A.
secondaryBelligerent
chosen
Indicates that an entity participates in a conflict as a secondary or supporting belligerent rather than as a primary combatant.
-
B.
hasBelligerentType
Indicates that an entity participates in a conflict in the specified role or category of belligerent.
-
C.
belligerentFor
Indicates a relationship in which one entity is engaged in hostile or aggressive behavior toward, or in conflict with, another entity.
-
D.
allegedBelligerent
Indicates that one entity is claimed or accused of being a hostile or warring party in relation to another entity or conflict.
-
E.
majorBelligerent
Indicates that an entity is a primary or principal participant in a conflict, war, or large-scale hostile engagement.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: April 27, 2026, 11:41 p.m.