Triple
T18444907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lehigh Mountain Hawks men's basketball |
E450628
|
entity |
| Predicate | opponentSeedIn2012Upset |
P105311
|
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: [Lehigh Mountain Hawks men's basketball, opponentSeedIn2012Upset, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentSeedIn2012Upset Context triple: [Lehigh Mountain Hawks men's basketball, opponentSeedIn2012Upset, 2]
-
A.
hasNotableUpsets
Indicates that one entity has achieved surprising or unexpected victories over another entity or entities.
-
B.
NCAATournamentRunnerUpFinishes
Indicates that a team finished as the runner-up (second place) in a specific NCAA Tournament.
-
C.
thirdSeedPlays
Indicates that the team or player seeded third participates in a game, match, or event.
-
D.
quarterFinalOpponent
Indicates that one entity is the opponent faced by another entity in a quarter-final stage of a competition or tournament.
-
E.
losingTeamSeed
chosen
Indicates the tournament seed or ranking assigned to the team that lost in a given game or matchup.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c142abc8190b4f6f938acdc413d |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:30 a.m.