Triple
T8691013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic 10 women's volleyball |
E206286
|
entity |
| Predicate | pointsToWinDecidingSet |
P55868
|
FINISHED |
| Object | 15 points |
—
|
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: 15 points | Statement: [Atlantic 10 women's volleyball, pointsToWinDecidingSet, 15 points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsToWinDecidingSet Context triple: [Atlantic 10 women's volleyball, pointsToWinDecidingSet, 15 points]
-
A.
pointsToWinSet
chosen
Indicates the number of points a player or side must win to secure the current set.
-
B.
pointsForWin
Indicates the number of points awarded to an entity for achieving a win in a given context or competition.
-
C.
numberOfWinsRequired
Indicates the specific count of wins an entity must achieve to meet a defined goal, threshold, or condition.
-
D.
decidingMatchFor
Indicates a relationship where one entity is chosen or determined as the appropriate or final match for another entity among possible alternatives.
-
E.
decidingGameWinner
Indicates that an event, action, or process determines which participant is the winner of 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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5735ffdc819094126e2698f98511 |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:33 p.m.