Triple
T8373002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia Tech Yellow Jackets men's basketball |
E197503
|
entity |
| Predicate | hasReachedNationalChampionshipGame |
P82367
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Georgia Tech Yellow Jackets men's basketball, hasReachedNationalChampionshipGame, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReachedNationalChampionshipGame Context triple: [Georgia Tech Yellow Jackets men's basketball, hasReachedNationalChampionshipGame, true]
-
A.
hasWonNCAATitleIn
Indicates that an entity has won an NCAA championship title in a specified sport, category, or year.
-
B.
numberOfNationalChampionships
Indicates the total count of national championship titles an entity has won.
-
C.
NCAATournamentAppearance
Indicates that an entity has participated in at least one NCAA basketball tournament.
-
D.
hasChampionshipGames
Indicates that an entity includes, hosts, or is associated with one or more championship-level games or matches.
-
E.
claimedNationalChampionshipSeason
Indicates that a team asserts or recognizes a particular season as one in which it won a national championship.
- 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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80a7cab881909d8cca66a340dceb |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6:01 p.m.