Triple
T32274093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | co-ACC regular season championship 2023 |
E824492
|
entity |
| Predicate | numberOfTeamsSharingTitle |
P203529
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [co-ACC regular season championship 2023, numberOfTeamsSharingTitle, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfTeamsSharingTitle Context triple: [co-ACC regular season championship 2023, numberOfTeamsSharingTitle, 2]
-
A.
isTitleNumberForTeam
Indicates that a given number represents the count of titles (e.g., championships or awards) associated with a specific team.
-
B.
teamOfTitle
Indicates that a given title or role is associated with, or belongs to, a particular team.
-
C.
mostTitlesTeamTitles
Indicates that the referenced team holds the highest number of titles compared to all other teams in the specified context.
-
D.
numberOfCombinedSeasonTitles
Indicates the total count of season titles jointly held or achieved together by the related entities.
-
E.
teamWithMultipleTitles
Indicates that a team has won more than one title or championship within the relevant competition or 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a019d1407588190b3b9b83fca2e61fe |
completed | May 11, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a019c760e3081909cfe9c0603727e48 |
completed | May 11, 2026, 9:08 a.m. |
| PDg | Predicate description generation | batch_6a019d12c1208190940abb0736c389b0 |
completed | May 11, 2026, 9:10 a.m. |
Created at: May 1, 2026, 12:42 a.m.