Triple
T5641642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Limerick |
E124279
|
entity |
| Predicate | concerned |
P11116
|
FINISHED |
| Object | political status of Irish Catholics |
—
|
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: political status of Irish Catholics | Statement: [Treaty of Limerick, concerned, political status of Irish Catholics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concerned Context triple: [Treaty of Limerick, concerned, political status of Irish Catholics]
-
A.
concern
chosen
Indicates that one entity is about, relates to, or is of interest or importance to another entity.
-
B.
concernedEvent
Indicates that an entity has a concern, involvement, or relevance specifically with respect to a particular event.
-
C.
raisedConcernAbout
Indicates that one entity has expressed worry, doubt, or objection regarding another entity or issue.
-
D.
strategicConcernFor
Indicates a relationship where one entity considers another entity’s situation, actions, or outcomes important for its own long-term goals, risks, or strategic interests.
-
E.
concernedProperty
Indicates that one entity is about, involves, or pertains to a particular property or attribute of 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c02286a14481908703ec1741343b76 |
completed | March 22, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.