Triple
T7828807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Basketball Tournament championship games |
E181312
|
entity |
| Predicate | prizeRecipient |
P45356
|
FINISHED |
| Object | winning team only |
—
|
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: winning team only | Statement: [The Basketball Tournament championship games, prizeRecipient, winning team only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prizeRecipient Context triple: [The Basketball Tournament championship games, prizeRecipient, winning team only]
-
A.
recipientOfAward
chosen
Indicates that an entity has received or been granted a particular award.
-
B.
hasLaureate
Indicates that an entity (such as an award or prize) has a specific person or group as its laureate or recipient.
-
C.
NobelPrizeCoLaureate
Indicates that two or more individuals share the same Nobel Prize as co-recipients for a particular award and year.
-
D.
coRecipientOfAward
Indicates that two or more entities jointly received the same award.
-
E.
namedAfterAwardLaureateOf
Indicates that one entity is named after a person who is a laureate (recipient) of a particular 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.