Triple
T36917217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 NCAA Men’s Final Four |
E913074
|
entity |
| Predicate | notableUpsetTeam |
P6985
|
FINISHED |
| Object | Loyola Ramblers men’s basketball team |
E416788
|
NE 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: Loyola Ramblers men’s basketball team | Statement: [2018 NCAA Men’s Final Four, notableUpsetTeam, Loyola Ramblers men’s basketball team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableUpsetTeam Context triple: [2018 NCAA Men’s Final Four, notableUpsetTeam, Loyola Ramblers men’s basketball team]
-
A.
notablePlayerWinningTeam
Indicates that a particular notable player was a member of the team that won a given competition or game.
-
B.
hasNotableUpsets
chosen
Indicates that one entity has achieved surprising or unexpected victories over another entity or entities.
-
C.
notableUpsetYear
Indicates the year in which a notable upset (an unexpected or surprising victory or outcome) occurred.
-
D.
game1LosingTeam
Indicates the team that lost in the first game of a series or event.
-
E.
notableRivalTeam
Indicates that one team is recognized as a significant or well-known rival of another team.
- F. None of above.
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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e2c29f6008190a49564e59360ca36 |
completed | June 26, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.