Triple
T31904995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1991 NCAA men's volleyball championship |
E814522
|
entity |
| Predicate | finalMatchSetsWonByChampion |
P190392
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [1991 NCAA men's volleyball championship, finalMatchSetsWonByChampion, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalMatchSetsWonByChampion Context triple: [1991 NCAA men's volleyball championship, finalMatchSetsWonByChampion, 3]
-
A.
winnerSetsWonInFinal
chosen
Indicates the number of sets won by the winning participant in the final match of a competition.
-
B.
championSeriesWins
Indicates that one entity has won a championship series a specified number of times or in a specified context relative to another entity.
-
C.
championFinalsRecord
Indicates the win–loss record a champion has specifically in finals appearances.
-
D.
finalChampion
Indicates that an entity is the ultimate winner or last remaining champion in a competition or series of contests.
-
E.
winForChampions
Indicates that the outcome of an event or competition results in a victory for the champions.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: May 1, 2026, midnight