Triple
T7819074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assembly of Ireland |
E181082
|
entity |
| Predicate | dateOfFirstMeeting |
P79179
|
FINISHED |
| Object | 21 January 1919 |
—
|
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: 21 January 1919 | Statement: [Assembly of Ireland, dateOfFirstMeeting, 21 January 1919]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFirstMeeting Context triple: [Assembly of Ireland, dateOfFirstMeeting, 21 January 1919]
-
A.
firstMeets
Indicates that one entity encounters or comes into contact with another entity for the first time.
-
B.
firstMeetingYear
Indicates the calendar year in which two entities first met or had their initial encounter.
-
C.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
D.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
E.
firstMeetingSeason
Indicates the season of the year during which two entities first met.
- 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_69ca828153f48190bdb27ac46f8e0745 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf97247c481908b18287eb7ee0a53 |
completed | March 30, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7855a3c81908b9318f7186fc0c0 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:40 p.m.