Triple
T2392968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 NCAA Women’s Final Four |
E48983
|
entity |
| Predicate | semifinalGame |
P36441
|
FINISHED |
| Object | South Carolina vs. Stanford |
—
|
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: South Carolina vs. Stanford | Statement: [2017 NCAA Women’s Final Four, semifinalGame, South Carolina vs. Stanford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: semifinalGame Context triple: [2017 NCAA Women’s Final Four, semifinalGame, South Carolina vs. Stanford]
-
A.
semifinalResult
Indicates the outcome or score of a semifinal-stage contest or match between competitors.
-
B.
semifinalMatchup
chosen
Indicates that two competitors or teams are paired to compete against each other in a semifinal round of a tournament or competition.
-
C.
semifinalGamesPlayedIn
Indicates that a given semifinal game took place at or within a specified location or venue.
-
D.
semifinalBowls
Indicates that the entities are the bowl games that serve as semifinal matchups in a tournament or playoff structure.
-
E.
semifinalDate
Indicates the scheduled calendar date on which a semifinal round of a competition or tournament takes place.
- 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc876d48881909e4d6f5ebe430012 |
completed | March 7, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.