Triple
T32349436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campobello Island raid |
E826552
|
entity |
| Predicate | conflictBelongsTo |
P1406
|
FINISHED |
| Object | Anglo-Irish conflict |
—
|
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: Anglo-Irish conflict | Statement: [Campobello Island raid, conflictBelongsTo, Anglo-Irish conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictBelongsTo Context triple: [Campobello Island raid, conflictBelongsTo, Anglo-Irish conflict]
-
A.
conflictRelation
Indicates a relationship in which two or more entities are in opposition, disagreement, or incompatibility, often involving competing goals, interests, or actions.
-
B.
conflictRole
Indicates that an entity plays a specific role or position within a conflict or dispute between parties.
-
C.
conflictResolvedBy
Indicates that a conflict or dispute is settled or addressed through the actions, decisions, or intervention of a specified entity or process.
-
D.
conflictIn
chosen
Indicates that one entity is involved in, associated with, or occurs within a particular 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 12:49 a.m.