Triple
T11708828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ormondist faction within Confederate Ireland |
E278315
|
entity |
| Predicate | typeOfConflictRole |
P5518
|
FINISHED |
| Object | negotiating 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: negotiating faction | Statement: [Ormondist faction within Confederate Ireland, typeOfConflictRole, negotiating faction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfConflictRole Context triple: [Ormondist faction within Confederate Ireland, typeOfConflictRole, negotiating faction]
-
A.
conflictRole
Indicates that an entity plays a specific role or position within a conflict or dispute between parties.
-
B.
conflictType
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
C.
conflictSpecific
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
-
D.
typicalConflict
Indicates that there is a commonly occurring or characteristic conflict or opposition between the related entities.
-
E.
typeOfRole
chosen
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a49de0388190a063739426bf90e8 |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7d483081909c2a101087515d74 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.