Triple
T9680964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magdalene Laundries |
E234279
|
entity |
| Predicate | apologyYear |
P19847
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Magdalene Laundries, apologyYear, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apologyYear Context triple: [Magdalene Laundries, apologyYear, 2013]
-
A.
apologyDate
chosen
Indicates the date on which an apology was made or formally recorded.
-
B.
pardonYear
Indicates the year in which a pardon was officially granted for an offense or conviction.
-
C.
claimedYear
Indicates the year that is asserted or reported as being associated with an event, status, or fact, regardless of whether it is verified.
-
D.
apologyIssued
Indicates that one entity has expressed regret or remorse to another entity for a perceived wrong, mistake, or offense.
-
E.
apologizedFor
Indicates that one entity expressed regret or remorse to another entity specifically about a particular action, event, or wrongdoing.
- 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_69ca84c99e34819092e5563a7106cfca |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9c9dcbe881908ae926a5b5eae759 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:16 p.m.