Triple
T14424946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division I Women's Tennis Championship |
E357671
|
entity |
| Predicate | teamTitleType |
P114220
|
FINISHED |
| Object | national team championship |
—
|
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: national team championship | Statement: [NCAA Division I Women's Tennis Championship, teamTitleType, national team championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamTitleType Context triple: [NCAA Division I Women's Tennis Championship, teamTitleType, national team championship]
-
A.
teamTitleBasis
Indicates that one entity serves as the basis or source for determining the title or name of a team associated with another entity.
-
B.
teamNameType
Indicates the type or category associated with a team's name (e.g., formal name, short name, nickname).
-
C.
leagueTitleCompanion
Indicates a relationship where one entity serves as an associated or companion title to another within the same league or competition context.
-
D.
teamCoachedToTitle
Indicates that a coach led a team to win a championship or title.
-
E.
teamName
Indicates the relationship that assigns or associates a specific name with a particular team.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91123f848190ba3fb18a76c2d24c |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:18 a.m.