Triple
T36388405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFQ Level 5 |
E896261
|
entity |
| Predicate | typicalExitQualification |
P106510
|
FINISHED |
| Object | Leaving Certificate |
E258374
|
NE 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: Leaving Certificate | Statement: [NFQ Level 5, typicalExitQualification, Leaving Certificate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalExitQualification Context triple: [NFQ Level 5, typicalExitQualification, Leaving Certificate]
-
A.
qualifyingReason
Indicates that one entity serves as the reason, basis, or justification for another entity’s qualification, status, or applicability.
-
B.
exitsAt
Indicates that one entity serves as the exit point or location where another entity leaves or departs.
-
C.
qualifyingFor
chosen
Indicates that one entity meets the necessary conditions or criteria to be eligible for another entity, status, or action.
-
D.
exitTo
Indicates that one location or entity serves as a passage or route leading directly to another location or entity.
-
E.
conditionForLeaving
Indicates the specific circumstance or requirement under which an entity is permitted or expected to leave a situation, place, or state.
- F. None of above.
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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39c3ffcb0c81908260ab99ecd3e279 |
completed | June 22, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.