Triple
T27571712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cy-Hawk Trophy |
E696052
|
entity |
| Predicate | winnerKeepsTrophyUntilNextGame |
P169567
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cy-Hawk Trophy, winnerKeepsTrophyUntilNextGame, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerKeepsTrophyUntilNextGame Context triple: [Cy-Hawk Trophy, winnerKeepsTrophyUntilNextGame, true]
-
A.
winnerReceives
Indicates that the entity identified as the winner is granted or awarded the specified item, benefit, or outcome as a result of winning.
-
B.
trophyWonBy
Indicates that a particular trophy or award is obtained or earned by a specific entity (such as a person or team).
-
C.
playoffTrophyContested
Indicates that a particular playoff trophy is the object of competition in a given playoff series or tournament.
-
D.
winnerPlaysIn
Indicates that the entity identified as the winner of a contest or match participates in a subsequent game, round, or event.
-
E.
namedAfterTrophy
Indicates that one entity has been given a name derived from or in honor of a particular trophy.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f67fc237608190b6542b56038a7fe4 |
completed | May 2, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 27, 2026, 1:43 p.m.