Triple
T28438622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian forces |
E715643
|
entity |
| Predicate | conflictParticipantIn |
P167916
|
FINISHED |
| Object | Russo-Turkish War (1828–1829) |
—
|
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: Russo-Turkish War (1828–1829) | Statement: [Russian forces, conflictParticipantIn, Russo-Turkish War (1828–1829)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictParticipantIn Context triple: [Russian forces, conflictParticipantIn, Russo-Turkish War (1828–1829)]
-
A.
partnerInConflictWith
Indicates that two entities are engaged as opposing partners or sides within the same conflict or dispute.
-
B.
partnerInConflictResolutionWith
Indicates that two entities collaborate as partners in resolving a specific conflict or dispute.
-
C.
hasPartOfConflict
Indicates that one conflict includes another conflict as a constituent or subordinate part of it.
-
D.
coupParticipantIn
Indicates that an entity took part in, contributed to, or was involved in carrying out a specific coup event.
-
E.
conflictRole
Indicates that an entity plays a specific role or position within a conflict or dispute between parties.
- 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f66e5f7e30819094530abceabd5f43 |
completed | May 2, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66d75a8788190aa9ca2c977429045 |
completed | May 2, 2026, 9:32 p.m. |
Created at: April 28, 2026, 1:44 a.m.