Triple
T22914047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitutionalist faction (early phase) |
E568679
|
entity |
| Predicate | typeOfConflictParticipant |
P375
|
FINISHED |
| Object | rebel faction |
—
|
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: rebel faction | Statement: [Constitutionalist faction (early phase), typeOfConflictParticipant, rebel faction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfConflictParticipant Context triple: [Constitutionalist faction (early phase), typeOfConflictParticipant, rebel faction]
-
A.
partnerInConflictWith
Indicates that two entities are engaged as opposing partners or sides within the same conflict or dispute.
-
B.
conflictRole
Indicates that an entity plays a specific role or position within a conflict or dispute between parties.
-
C.
conflictSide
chosen
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
D.
partnerInConflictResolutionWith
Indicates that two entities collaborate as partners in resolving a specific conflict or dispute.
-
E.
conflictType
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1807668c481908494769bab9c8f1d |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.