Triple
T5626195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Women’s Final Four |
E147722
|
entity |
| Predicate | hasChampionshipGames |
P65498
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [NCAA Women’s Final Four, hasChampionshipGames, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChampionshipGames Context triple: [NCAA Women’s Final Four, hasChampionshipGames, 1]
-
A.
playsChampionshipGame
Indicates that an entity participates as a competitor in a championship-level game or match.
-
B.
hasFootballChampionshipGame
Indicates that an entity hosts, organizes, or is associated with a football championship game.
-
C.
hasChampionshipMatch
Indicates that an entity is associated with a specific championship-level match, typically as an organizer, participant, or host.
-
D.
hasChampionships
Indicates that one entity possesses or has won one or more championships associated with another entity.
-
E.
conferenceChampionshipAppearancesThrough2023
Indicates the number of times an entity has appeared in conference championship games or series up to and including the 2023 season.
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02237dd6081909f6a7d710b9cd651 |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f40df64819089a659ea00a835ef |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:40 p.m.