Triple
T20723871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albus Severus Potter |
E509384
|
entity |
| Predicate | schoolYearStart |
P141264
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Albus Severus Potter, schoolYearStart, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schoolYearStart Context triple: [Albus Severus Potter, schoolYearStart, 2017]
-
A.
schoolYear
Indicates the academic year or grade level in which an entity (typically a student or class) is situated within an educational system.
-
B.
typicalAcademicYearStart
Indicates the usual calendar date or period when an academic year customarily begins for an institution or system.
-
C.
effectiveInSchoolYear
Indicates that something (such as a policy, program, or status) is in force or applicable during a specified school year.
-
D.
hasSchoolYearEndMonth
Indicates the month in which a school year ends for a given educational institution or system.
-
E.
operatesInSchoolYearSystem
Indicates that an entity functions according to, or is organized around, a specific school year calendar or system.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1e662f08190917ee043612d413e |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:28 p.m.