Triple
T7828745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Basketball Tournament |
E181310
|
entity |
| Predicate | prizeDistribution |
P10713
|
FINISHED |
| Object | only champion receives main prize |
—
|
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: only champion receives main prize | Statement: [The Basketball Tournament, prizeDistribution, only champion receives main prize]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prizeDistribution Context triple: [The Basketball Tournament, prizeDistribution, only champion receives main prize]
-
A.
prizeContext
chosen
Indicates the situational or contextual circumstances under which a prize is awarded, considered, or relevant.
-
B.
prizeType
Indicates the specific category or kind of prize associated with an entity or event.
-
C.
prizeOfficialName
Indicates the formal, officially recognized name assigned to a prize.
-
D.
isPrizedFor
Indicates that something is highly valued or esteemed because of a particular quality, feature, or benefit it provides.
-
E.
awardIncludes
Indicates that a particular award encompasses, contains, or is composed of the specified component, category, or sub-award.
- 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb04aaed1881908e1da129a43ef9c7 |
completed | March 30, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:43 p.m.