Triple
T26068826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major Series Lacrosse |
E657482
|
entity |
| Predicate | championshipTrophyContested |
P101635
|
FINISHED |
| Object | Mann Cup |
—
|
NE NERFINISHED |
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: Mann Cup | Statement: [Major Series Lacrosse, championshipTrophyContested, Mann Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championshipTrophyContested Context triple: [Major Series Lacrosse, championshipTrophyContested, Mann Cup]
-
A.
championshipFor
Indicates that a championship event or title is held, awarded, or designated for a particular competition, season, or category.
-
B.
isFormerChampionshipTrophyOf
Indicates that an object previously served as the official championship trophy awarded for a particular competition or title.
-
C.
trophyContestedBy
Indicates that a particular trophy is the object of competition among the specified participants or teams.
-
D.
championshipStatus
Indicates the competitive or title-holding state of an entity within a championship or league context.
-
E.
primaryChampionshipContested
chosen
Indicates that a competition or event involves the contesting of a primary or main championship title between participants.
- 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_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 7:27 p.m.