Triple
T13575955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selke Trophy |
E324285
|
entity |
| Predicate | recordHoldersMostWinsNumber |
P7620
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [Selke Trophy, recordHoldersMostWinsNumber, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordHoldersMostWinsNumber Context triple: [Selke Trophy, recordHoldersMostWinsNumber, 6]
-
A.
mostOverallWinsRecord
chosen
Indicates that the subject holds the record for having the greatest total number of wins compared to all others in the relevant context.
-
B.
recordHolderAwardsCount
Indicates the number of awards held by the entity that currently holds a particular record.
-
C.
mostOverallWinsHolder
Indicates that the subject is the entity holding the highest total number of wins overall, compared to all other relevant entities.
-
D.
isAllTimeRecordHolderFor
Indicates that an entity holds the highest or best performance record of all time for a particular category, event, or metric.
-
E.
mostGamesWonBy
Indicates that one entity holds the record for having won the greatest number of games compared to others in a given context.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb02b1f108190a12af382d1de70bb |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.