Triple
T14946598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big 12 Conference Tournament |
E372677
|
entity |
| Predicate | sportRules |
P116786
|
FINISHED |
| Object | NCAA men's basketball rules |
—
|
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: NCAA men's basketball rules | Statement: [Big 12 Conference Tournament, sportRules, NCAA men's basketball rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportRules Context triple: [Big 12 Conference Tournament, sportRules, NCAA men's basketball rules]
-
A.
sportEventType
Indicates the specific kind or category of sport associated with a given sporting event.
-
B.
esportDiscipline
Indicates that one entity is a specific esports game or discipline in which the other entity participates or is involved.
-
C.
sportTypeGoverned
Indicates that a governing body or organization has regulatory authority over a particular type of sport.
-
D.
sportCategory
Indicates that one entity is classified as a type or category of sport to which the other entity (typically a specific sport or sporting event) belongs.
-
E.
sportNumber
Indicates the specific jersey or uniform number associated with an athlete in a sporting context.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded68e35c481908e47cd68441c5115 |
completed | April 15, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:39 a.m.