Triple
T24021897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jake Ellenberger |
E594844
|
entity |
| Predicate | hasWonByMethod |
P154896
|
FINISHED |
| Object | knockout |
—
|
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: knockout | Statement: [Jake Ellenberger, hasWonByMethod, knockout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWonByMethod Context triple: [Jake Ellenberger, hasWonByMethod, knockout]
-
A.
hasWinningScore
Indicates that one entity possesses a score that is sufficient to win in a given competition, game, or scoring context.
-
B.
wonBy
Indicates that a contest, game, or competition is decided in favor of a particular participant or side.
-
C.
hasWonSeries
Indicates that one entity has achieved overall victory in a multi-game or multi-event series against another entity.
-
D.
hasWinnerType
Indicates that an entity has a specific type or category of winner associated with it.
-
E.
hasWonCompetition
Indicates that an entity has achieved victory in a competition or contest against others.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d7667ff08190bfd14aa4eb776f21 |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 9:51 p.m.