Triple
T28839521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hogwarts Quidditch Cup |
E728274
|
entity |
| Predicate | notHeldInYear |
P89288
|
FINISHED |
| Object | 1994–1995 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: 1994–1995 school year | Statement: [Hogwarts Quidditch Cup, notHeldInYear, 1994–1995 school year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notHeldInYear Context triple: [Hogwarts Quidditch Cup, notHeldInYear, 1994–1995 school year]
-
A.
notHeldFollowingYear
Indicates that an event or activity that occurred in one year did not take place in the immediately following year.
-
B.
notHeldIn
chosen
Indicates that an event, activity, or state does not take place or is not located within a specified context, location, or time frame.
-
C.
notHeldDuring
Indicates that a specified condition, event, or relationship does not occur or is not in effect throughout a given time interval or temporal context.
-
D.
didNotHold
Indicates that an expected event, condition, or relationship failed to occur or be valid.
-
E.
reasonNotHeldPreviousYear
Indicates that there was a specific reason why something did not take place or was not held in the previous year.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6597132cc8190a9a2fd336fd2d084 |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:40 a.m.