Triple
T34578717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Griz |
E887830
|
entity |
| Predicate | hasRivalryGameTrophy |
P47111
|
FINISHED |
| Object | Great Divide Trophy |
—
|
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: Great Divide Trophy | Statement: [Griz, hasRivalryGameTrophy, Great Divide Trophy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRivalryGameTrophy Context triple: [Griz, hasRivalryGameTrophy, Great Divide Trophy]
-
A.
hasRivalryTrophyStatus
Indicates that a rivalry trophy has a particular status or condition within the context of a competitive relationship.
-
B.
isRivalryTrophyFor
chosen
Indicates that an object serves as the trophy awarded in a rivalry competition between specific entities.
-
C.
hasTrophyStatus
Indicates that an entity possesses a particular trophy-related status or classification.
-
D.
isPlayoffTrophyOf
Indicates that a trophy is awarded to and associated with a particular team or competition as the result of a playoff victory.
-
E.
hasRelatedTrophy
Indicates that there exists a trophy that is associated with, linked to, or relevant to the given entity.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 1, 2026, 2:03 a.m.