Triple
T11044293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Certificate of Educational Achievement |
E261098
|
entity |
| Predicate | fullyImplementedByYear |
P90584
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [National Certificate of Educational Achievement, fullyImplementedByYear, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullyImplementedByYear Context triple: [National Certificate of Educational Achievement, fullyImplementedByYear, 2004]
-
A.
dateImplemented
chosen
Indicates the date on which something (such as a plan, rule, feature, or system) was put into effect or made operational.
-
B.
yearOfDevelopment
Indicates the specific year in which something was developed or created.
-
C.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
-
D.
historicallyImplementedIn
Indicates that an action, practice, or system was carried out or put into effect in a particular place or context during a past historical period.
-
E.
originalCompletionYear
Indicates the year in which something (such as a project, work, or construction) was first fully completed.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7982e08548190aec04099cef9453c |
completed | April 9, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.