Triple
T3854561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA women's volleyball |
E85380
|
entity |
| Predicate | setWinCondition |
P20842
|
FINISHED |
| Object | 25 points with 2-point margin |
—
|
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: 25 points with 2-point margin | Statement: [NCAA women's volleyball, setWinCondition, 25 points with 2-point margin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setWinCondition Context triple: [NCAA women's volleyball, setWinCondition, 25 points with 2-point margin]
-
A.
conditionOfVictory
chosen
Indicates the specific circumstances or criteria under which a participant is considered to have won.
-
B.
numberOfWinsRequired
Indicates the specific count of wins an entity must achieve to meet a defined goal, threshold, or condition.
-
C.
winnerState
Indicates the state or condition of an entity that has achieved victory or been declared the winner in a given context.
-
D.
pointsForWin
Indicates the number of points awarded to an entity for achieving a win in a given context or competition.
-
E.
gameWinningScoreType
Indicates the type or category of score (e.g., goal, point, run) that results in winning a game.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec05ec4c8190bd5e5463163712dc |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee752c8a48190a670f73ed0bf1e61 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.