Triple
T28839522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hogwarts Quidditch Cup |
E728274
|
entity |
| Predicate | notHeldReason |
P165994
|
FINISHED |
| Object | Triwizard Tournament |
—
|
NE NERFINISHED |
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: Triwizard Tournament | Statement: [Hogwarts Quidditch Cup, notHeldReason, Triwizard Tournament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notHeldReason Context triple: [Hogwarts Quidditch Cup, notHeldReason, Triwizard Tournament]
-
A.
reasonNextNotHeld
Indicates that the specified reason explains why the immediately following event, state, or condition did not occur or was not maintained.
-
B.
notHeldIn
Indicates that an event, activity, or state does not take place or is not located within a specified context, location, or time frame.
-
C.
notAutomaticallyHeldBy
Indicates that a particular right, status, or condition is not granted or possessed by default and must be explicitly obtained or established.
-
D.
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.
-
E.
didNotHold
Indicates that an expected event, condition, or relationship failed to occur or be valid.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65bb75cd08190bbdb63c093ad6210 |
completed | May 2, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65b136b30819090cf59fb772f35f1 |
completed | May 2, 2026, 8:14 p.m. |
Created at: April 28, 2026, 6:40 a.m.