Triple
T34458474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pac-12 men's basketball season |
E884566
|
entity |
| Predicate | conferenceTournamentFormat |
P2673
|
FINISHED |
| Object | single-elimination |
—
|
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: single-elimination | Statement: [Pac-12 men's basketball season, conferenceTournamentFormat, single-elimination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceTournamentFormat Context triple: [Pac-12 men's basketball season, conferenceTournamentFormat, single-elimination]
-
A.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
B.
tourFormat
Indicates the specific structure, style, or type of a tour associated with an entity.
-
C.
NCAATournamentFormat
Indicates the specific structure, rules, and progression format used to organize and conduct the NCAA tournament.
-
D.
teamSportFormat
Indicates the type or structure of how a sport is organized and played as a team-based competition.
-
E.
formerConferenceTournament
Indicates that an entity previously served as the conference tournament for another entity but no longer holds that status.
- 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_69f349c73a94819094dfcf50d00620b8 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 1, 2026, 2 a.m.