Triple
T20178884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uno |
E492671
|
entity |
| Predicate | typicalWinningScore |
P29755
|
FINISHED |
| Object | 500 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: 500 points | Statement: [Uno, typicalWinningScore, 500 points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWinningScore Context triple: [Uno, typicalWinningScore, 500 points]
-
A.
gameWinningScoreBy
Indicates that a particular score is the decisive amount by which a game is won by an entity.
-
B.
gameWinningScore
chosen
Indicates that a particular score results in winning the game.
-
C.
gameWinningScoreType
Indicates the type or category of score (e.g., goal, point, run) that results in winning a game.
-
D.
typicalWinningScoreRelativeToPar
Indicates the usual or expected winning score in relation to the course’s par (e.g., how many strokes under or over par typically wins).
-
E.
winningTeamScore
Indicates the number of points or goals achieved by the team that wins a particular game or competition.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668ed07c8819091bd9ffda237a91c |
completed | April 20, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:36 p.m.