Triple
T19929525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACC baseball tournament |
E479013
|
entity |
| Predicate | teamSelectionBasis |
P31058
|
FINISHED |
| Object | ACC regular season performance |
—
|
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: ACC regular season performance | Statement: [ACC baseball tournament, teamSelectionBasis, ACC regular season performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamSelectionBasis Context triple: [ACC baseball tournament, teamSelectionBasis, ACC regular season performance]
-
A.
squadSelectionBasis
Indicates the criterion or rationale used to choose which individuals are included in a particular squad or team.
-
B.
teamSelection
chosen
Indicates the assignment or choice of one or more individuals or entities to be part of a specific team.
-
C.
captainSelectionBasis
Indicates the criteria or basis on which an individual is chosen or designated to serve as captain.
-
D.
AllWNBATeamSelection
Indicates that a player has been selected to an All-WNBA Team for a given season or time period.
-
E.
MVPSelectionBasis
Indicates the criteria or factors used to determine why a particular entity is chosen as the Most Valuable Player (MVP).
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659cd4500819090363a4b7d6bf193 |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.