Triple
T24253964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wexford Rebellion |
E603610
|
entity |
| Predicate | insurgentForce |
P32429
|
FINISHED |
| Object | United Irishmen |
—
|
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 Irishmen | Statement: [Wexford Rebellion, insurgentForce, United Irishmen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: insurgentForce Context triple: [Wexford Rebellion, insurgentForce, United Irishmen]
-
A.
rebelInstitution
chosen
Indicates that an institution actively resists, opposes, or defies an established authority, system, or governing power.
-
B.
insurgentSupporter
Indicates that one entity supports, assists, or aligns with an insurgent group or insurgent activities.
-
C.
insurgentCapital
Indicates a relationship where a location functions as the primary base, stronghold, or central hub of operations for an insurgent group.
-
D.
endedInsurgencyType
Indicates the specific manner or category of outcome by which an insurgency was brought to an end.
-
E.
offensiveForce
Indicates the use or application of aggressive or attacking power or violence by one entity against another.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b8bcb1c8190995e464a5f85fba9 |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:05 a.m.