Triple
T24744761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drake Relays |
E618662
|
entity |
| Predicate | attractsAthletesFrom |
P30111
|
FINISHED |
| Object | Canada |
E14901
|
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: Canada | Statement: [Drake Relays, attractsAthletesFrom, Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attractsAthletesFrom Context triple: [Drake Relays, attractsAthletesFrom, Canada]
-
A.
athletesFrom
Indicates that one or more athletes originate from, represent, or are associated with a particular place or organization.
-
B.
athleteRecruitmentFrom
Indicates that an athlete was recruited from a particular source, such as a school, team, or location.
-
C.
athletesVillage
Indicates the location or association of athletes with a designated residential village, typically used for housing them during an event or competition.
-
D.
attractsParticipantsFrom
chosen
Indicates that an event, activity, or organization draws or recruits participants originating from a specified place, group, or source.
-
E.
attractsTeamsFrom
Indicates that an entity draws or pulls in teams from another specified entity or location.
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a101bdde74881908b89bbc17ad0c0e6 |
completed | May 22, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:21 a.m.