Triple
T19042774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton Skyhawks |
E466047
|
entity |
| Predicate | partOfSports |
P134853
|
FINISHED |
| Object | Canadian basketball history |
—
|
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: Canadian basketball history | Statement: [Hamilton Skyhawks, partOfSports, Canadian basketball history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfSports Context triple: [Hamilton Skyhawks, partOfSports, Canadian basketball history]
-
A.
relatedSport
Indicates that there is an association or connection between an entity and a particular sport.
-
B.
basedInSport
Indicates that an entity (such as a team, organization, or person) is primarily associated with or operates within a particular sport.
-
C.
partOfMultiSportEvent
Indicates that an event or competition is included as one component within a larger multi-sport event.
-
D.
tenantSport
Indicates that a tenant participates in or is associated with a particular sport.
-
E.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
- F. None of above. chosen
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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d801ef188190a231e85e1bbce037 |
completed | April 20, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4c0fc3c4c8190abbfe06e1bd3325c |
completed | April 19, 2026, 11:48 a.m. |
Created at: April 10, 2026, 12:03 p.m.