Triple
T22852461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2006–07 Grand Prix Final |
E566388
|
entity |
| Predicate | shortProgramDateMen |
P135143
|
FINISHED |
| Object | 2006-12-14 |
—
|
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: 2006-12-14 | Statement: [2006–07 Grand Prix Final, shortProgramDateMen, 2006-12-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shortProgramDateMen Context triple: [2006–07 Grand Prix Final, shortProgramDateMen, 2006-12-14]
-
A.
eventsForMen
Indicates that the associated events are specifically designated for male participants.
-
B.
mainEventDate
Indicates the primary or most significant date on which the referenced event occurs or is scheduled to occur.
-
C.
eventDateContext
chosen
Indicates the contextual role or significance that a specific date has within an event (e.g., whether it is the start, end, deadline, or another relevant temporal marker).
-
D.
madeProgram
Indicates that one entity created, developed, or authored a program (such as software or a coded application).
-
E.
outcomeForMen
Indicates the specific result, effect, or consequence that an event, action, or condition has for men.
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eb9a5b8819091cbb4ac42fbf778 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:36 p.m.