Triple
T13708943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch Super Cup |
E328717
|
entity |
| Predicate | usuallyHeldIn |
P17057
|
FINISHED |
| Object | August |
—
|
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: August | Statement: [Dutch Super Cup, usuallyHeldIn, August]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usuallyHeldIn Context triple: [Dutch Super Cup, usuallyHeldIn, August]
-
A.
typicallyHeldIn
chosen
Indicates that an event, activity, or process most commonly or usually takes place within a particular location, venue, or context.
-
B.
oftenHeldOn
Indicates that an event or activity typically takes place on a particular date, day, or time.
-
C.
officeHeldIn
Indicates that a particular office or position is held within or associated with a specific geographic or administrative location.
-
D.
areHeldIn
Indicates that events, activities, or objects take place or are located within a particular venue, container, or setting.
-
E.
oftenHeldAs
Indicates that one entity is frequently regarded, considered, or believed to be in a particular way with respect to another entity or property.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad18d48c8190a26be865c31975d6 |
completed | April 13, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.