Triple
T26068906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peterborough Lakers |
E657484
|
entity |
| Predicate | hasWonChampionshipType |
P73147
|
FINISHED |
| Object | Canadian senior men's box lacrosse championship |
—
|
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 senior men's box lacrosse championship | Statement: [Peterborough Lakers, hasWonChampionshipType, Canadian senior men's box lacrosse championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWonChampionshipType Context triple: [Peterborough Lakers, hasWonChampionshipType, Canadian senior men's box lacrosse championship]
-
A.
hasChampionships
Indicates that one entity possesses or has won one or more championships associated with another entity.
-
B.
hasWonTitleType
chosen
Indicates that an entity has won a title of a specified type.
-
C.
hasWonMultipleChampionships
Indicates that the subject has secured championship titles on more than one separate occasion.
-
D.
teamWonChampionship
Indicates that a particular team has secured victory in a championship competition.
-
E.
hasWonPlayersChampionship
Indicates that the subject has won The Players Championship golf tournament at least once.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 26, 2026, 7:27 p.m.