Triple
T32420530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Splash! |
E828445
|
entity |
| Predicate | notableAthleteMentor |
P550
|
FINISHED |
| Object | Olympic diver Tom Daley |
E185023
|
NE 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: Olympic diver Tom Daley | Statement: [Splash!, notableAthleteMentor, Olympic diver Tom Daley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAthleteMentor Context triple: [Splash!, notableAthleteMentor, Olympic diver Tom Daley]
-
A.
notableAthlete
Indicates that the subject is a well-known or distinguished athlete associated with the object (such as a sport, team, or organization).
-
B.
notableAthleteFrom
Indicates that an athlete is notably associated with or originates from a particular place or region.
-
C.
notableCoach
chosen
Indicates that one entity is a coach who is widely recognized or distinguished in relation to the other entity.
-
D.
notableCoachAlumnus
Indicates that a person is a notable former player or trainee of a particular coach.
-
E.
notableCharacterSport
Indicates that a notable character is associated with, participates in, or is prominently linked to a particular sport.
- F. None of above.
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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34e4ec6908819093d758c35ff1b61f |
completed | June 19, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:54 a.m.