Triple
T10937529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leaving Certificate |
E258374
|
entity |
| Predicate | resultsReleasedIn |
P96730
|
FINISHED |
| Object | August |
—
|
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: August | Statement: [Leaving Certificate, resultsReleasedIn, August]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultsReleasedIn Context triple: [Leaving Certificate, resultsReleasedIn, August]
-
A.
resultsPublishedBy
Indicates that the results of an activity, process, or event are made publicly available or formally issued by a particular agent or organization.
-
B.
someReleasedTo
Indicates that at least one instance of an item or entity has been released or made available to a specified recipient or target.
-
C.
releasedThrough
Indicates that something (such as a work, product, or content) is made publicly available or distributed via a particular channel, platform, or intermediary.
-
D.
resultsReportedAs
Indicates that the outcomes or findings of an activity, process, or evaluation are communicated or documented in a specified form, format, or medium.
-
E.
alsoReleased
Indicates that two or more items were released at the same time or as part of the same release event.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770b065288190b4216beee8e8a193 |
completed | April 9, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69d72e816a98819096d6c10dfb88a66a |
completed | April 9, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69d7322370648190ba14cdd6fb4cdcb0 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:23 p.m.