Triple
T16941066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old IRA |
E410949
|
entity |
| Predicate | claimedLoyaltyTo |
P94124
|
FINISHED |
| Object | Irish Republic proclaimed in 1916 |
—
|
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: Irish Republic proclaimed in 1916 | Statement: [Old IRA, claimedLoyaltyTo, Irish Republic proclaimed in 1916]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedLoyaltyTo Context triple: [Old IRA, claimedLoyaltyTo, Irish Republic proclaimed in 1916]
-
A.
isLoyalTo
chosen
Indicates that one entity consistently supports, respects, or remains faithful to another entity.
-
B.
loyaltyRevealedIn
Indicates that an entity’s loyalty becomes evident or is demonstrated through a particular situation, action, or context.
-
C.
loyaltySymbolizedBy
Indicates that an instance of loyalty is represented or expressed by a particular symbol or emblem.
-
D.
loyaltyReason
Indicates the reason or motivation behind one entity’s loyalty or allegiance to another.
-
E.
loyaltyConflict
Indicates a situation where an entity’s loyalties to different people, groups, or principles are in tension or opposition, creating a conflict in choosing whom or what to support.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfacdbc48190988ac259712bb9e8 |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.