Triple
T23690426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Castlebar |
E585281
|
entity |
| Predicate | involvedIrishRebels |
P107017
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Battle of Castlebar, involvedIrishRebels, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedIrishRebels Context triple: [Battle of Castlebar, involvedIrishRebels, true]
-
A.
IrishVolunteersStrength
Indicates the number or level of manpower associated with the Irish Volunteers.
-
B.
successorAsDominantForceInIrishNationalism
Indicates that one entity has replaced another as the leading or most influential force within the movement of Irish nationalism.
-
C.
roleOfIrishForces
Indicates the specific function, duties, or involvement assigned to Irish forces within a particular context or operation.
-
D.
rebelInstitution
Indicates that an institution actively resists, opposes, or defies an established authority, system, or governing power.
-
E.
rebelsAgainst
chosen
Indicates that one entity actively resists, opposes, or rises up against the authority, control, or established order represented by another entity.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5c16af08190b2f4d126c60a7e75 |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.