Triple
T8189250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamond Jubilee Challenge Cup |
E191262
|
entity |
| Predicate | timingOfEvent |
P35710
|
FINISHED |
| Object | held in early July |
—
|
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: held in early July | Statement: [Diamond Jubilee Challenge Cup, timingOfEvent, held in early July]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timingOfEvent Context triple: [Diamond Jubilee Challenge Cup, timingOfEvent, held in early July]
-
A.
timePeriodEvent
chosen
Indicates that an event occurs, is scheduled, or is valid within a specified time period.
-
B.
timingOfRace
Indicates the temporal details or schedule associated with a race, such as its start time, duration, or overall timing.
-
C.
timeOfCelebration
Indicates the specific time or period during which a celebration takes place.
-
D.
eventOccurredAt
Indicates that a particular event took place at a specific time or location.
-
E.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4da0e1288190b9c7c1d3b9a98830 |
completed | March 31, 2026, 4:29 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:41 p.m.