Triple
T26838948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hong Kong Diploma of Secondary Education curriculum |
E675716
|
entity |
| Predicate | startGrade |
P105748
|
FINISHED |
| Object | Secondary 4 |
—
|
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: Secondary 4 | Statement: [Hong Kong Diploma of Secondary Education curriculum, startGrade, Secondary 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startGrade Context triple: [Hong Kong Diploma of Secondary Education curriculum, startGrade, Secondary 4]
-
A.
gradeRangeStart
chosen
Indicates the lower boundary value at which a particular grade or grading interval begins.
-
B.
gradeIn
Indicates that an entity has a particular grade or score within a specified course, assignment, or evaluation context.
-
C.
gradeWithin
Indicates that one value’s grade or level falls within a specified range or interval relative to another.
-
D.
gradeCategory
Indicates the classification of a grade into a broader category or level (such as letter grade, performance band, or pass/fail group).
-
E.
introducedAsGrade
Indicates that one entity was presented or designated to another specifically in the role or capacity of a particular grade or level.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 27, 2026, 5:06 a.m.