Triple
T30973050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 U.S. Men’s Clay Court Championships – singles |
E789151
|
entity |
| Predicate | finalSetScore |
P194663
|
FINISHED |
| Object | first set 6–4 |
—
|
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: first set 6–4 | Statement: [2011 U.S. Men’s Clay Court Championships – singles, finalSetScore, first set 6–4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalSetScore Context triple: [2011 U.S. Men’s Clay Court Championships – singles, finalSetScore, first set 6–4]
-
A.
finalScore
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
B.
finalReplayScore
Indicates the score or result achieved at the end of a replayed event, game, or scenario.
-
C.
finalScoreWinner
Indicates that the referenced entity is the winner as determined by the final score of a game, match, or competition.
-
D.
finalScoreNote
Indicates a note or comment specifically associated with the final score or outcome of an evaluation, game, or assessment.
-
E.
finalSecondLegScore
Indicates the score achieved in the second leg of a two-leg competition or matchup once that leg is completed.
- F. None of above. chosen
Provenance (4 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
| PDg | Predicate description generation | batch_69fd7fd9be2881908a7f00e0e8822de8 |
completed | May 8, 2026, 6:16 a.m. |
Created at: April 29, 2026, 8:55 p.m.