Triple
T31904996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1991 NCAA men's volleyball championship |
E814522
|
entity |
| Predicate | finalMatchSetsWonByRunnerUp |
P185434
|
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: [1991 NCAA men's volleyball championship, finalMatchSetsWonByRunnerUp, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalMatchSetsWonByRunnerUp Context triple: [1991 NCAA men's volleyball championship, finalMatchSetsWonByRunnerUp, 1]
-
A.
runnerUpSetsWonInFinal
chosen
Indicates the number of sets won by the runner-up in the final match of a competition.
-
B.
gamesWonByRunnerUp
Indicates the number of games won by the runner-up in a competition or match.
-
C.
finalMatches
Indicates that two or more items correspond exactly in their final or completed form, satisfying all criteria for being considered the same at the end state.
-
D.
winnerSetsWonInFinal
Indicates the number of sets won by the winning participant in the final match of a competition.
-
E.
finishedRunnersUpIn
Indicates that one entity concluded a competition or contest in the runners-up position relative to another entity or event.
- 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_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 1, 2026, midnight