Triple
T4152716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division I Men’s Tennis Championship |
E89943
|
entity |
| Predicate | teamDrawFormat |
P2673
|
FINISHED |
| Object | single-elimination |
—
|
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: single-elimination | Statement: [NCAA Division I Men’s Tennis Championship, teamDrawFormat, single-elimination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamDrawFormat Context triple: [NCAA Division I Men’s Tennis Championship, teamDrawFormat, single-elimination]
-
A.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
B.
leagueDraws
Indicates that a league competition or season resulted in a specified number of drawn (tied) matches.
-
C.
matchPointsDraw
Indicates that the entities receive or share an equal number of points as a result of a drawn or tied match.
-
D.
hasHomeAndAwayFormat
Indicates that a competition, match, or series is structured with both home and away legs or fixtures between the same opponents.
-
E.
teamRepresentation
Indicates that one entity serves as the official representative or embodiment of a team in a given context or activity.
- 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_69aed95a59a881909b26e70b42c6811a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af033ef6648190adde17f943d89c78 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018c101081909070da5b11e5eb3d |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.