Triple
T3737007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | anti-Treaty IRA |
E79608
|
entity |
| Predicate | positionOnTreaty |
P45755
|
FINISHED |
| Object | rejected Anglo-Irish Treaty of 1921 |
—
|
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: rejected Anglo-Irish Treaty of 1921 | Statement: [anti-Treaty IRA, positionOnTreaty, rejected Anglo-Irish Treaty of 1921]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnTreaty Context triple: [anti-Treaty IRA, positionOnTreaty, rejected Anglo-Irish Treaty of 1921]
-
A.
positionOnSecurityTreaty
chosen
Indicates the stance or viewpoint an entity holds regarding a specific security treaty.
-
B.
linkedToTreaty
Indicates that an entity has a formal connection or association with a specific treaty, such as being established by, governed by, or otherwise related to that treaty.
-
C.
relevantSectionForTreaty
Indicates that a specific legal or textual section is pertinent or applicable to a given treaty.
-
D.
treatySignedPlace
Indicates the location where a treaty was formally signed or concluded.
-
E.
treatyFocus
Indicates that a treaty is primarily concerned with, directed toward, or centered on a particular subject, issue, or area.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb3d32b081909a993a78b0869db8 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.