Triple
T37637649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confederate Catholic army |
E936530
|
entity |
| Predicate | provinceCommand |
P198376
|
FINISHED |
| Object | Leinster army |
—
|
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: Leinster army | Statement: [Confederate Catholic army, provinceCommand, Leinster army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provinceCommand Context triple: [Confederate Catholic army, provinceCommand, Leinster army]
-
A.
provinceCivil
Indicates that a province is involved in a civil (non-criminal) legal or administrative matter related to another entity.
-
B.
province
Indicates that one entity is an administrative subdivision or region (a province) governed by or belonging to another, typically larger, political or territorial entity.
-
C.
provinceOfficial
Indicates that an individual holds an official governmental position within a specific province.
-
D.
provinceHead
Indicates that one entity serves as the administrative leader or governing head of a specified province.
-
E.
provinceSide
Indicates that one entity is a side or bordering region of a province in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69fedfd850ec81909b55f90dc850167e |
completed | May 9, 2026, 7:18 a.m. |
Created at: May 3, 2026, 4:18 p.m.