Triple
T36412872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magical Me |
E896927
|
entity |
| Predicate | schoolYearUsed |
P69189
|
FINISHED |
| Object | 1992–1993 school year |
—
|
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: 1992–1993 school year | Statement: [Magical Me, schoolYearUsed, 1992–1993 school year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schoolYearUsed Context triple: [Magical Me, schoolYearUsed, 1992–1993 school year]
-
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.
schoolYearStart
Indicates the point in time or date when a particular school year begins.
-
C.
effectiveInSchoolYear
chosen
Indicates that something (such as a policy, program, or status) is in force or applicable during a specified school year.
-
D.
hasSchoolYears
Indicates a relationship where an educational institution is associated with specific academic years or grade levels it offers or covers.
-
E.
hasSchoolYearStructure
Indicates that an educational institution follows or is organized according to a particular school year structure or calendar pattern.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.