Triple
T412510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivy League Men’s Basketball Tournament |
E9519
|
entity |
| Predicate | finalists |
P11194
|
FINISHED |
| Object | winners of the two semifinals |
—
|
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: winners of the two semifinals | Statement: [Ivy League Men’s Basketball Tournament, finalists, winners of the two semifinals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalists Context triple: [Ivy League Men’s Basketball Tournament, finalists, winners of the two semifinals]
-
A.
runnerUp
Indicates that one entity finished in second place relative to another in a competition or ranking.
-
B.
mainCandidates
Indicates that the referenced entities are the primary or most prominent candidates within a given selection or context.
-
C.
finalsChampion
Indicates that an entity is the winner or champion of a particular final match, series, or tournament.
-
D.
featuredCandidate
Indicates that a particular candidate is highlighted or given special prominence relative to others.
-
E.
nominated
Indicates that one entity formally proposes or selects another entity for a position, role, award, or recognition.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecdafa2481908111accc918ff2e8 |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e9749234819084b0ce94faabd0b1 |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ea60e590819081779a6510918d9b |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.