Triple
T20231821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benjamin Becker |
E495542
|
entity |
| Predicate | ATPFinalsReachedSingles |
P139333
|
FINISHED |
| Object | 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: 4 | Statement: [Benjamin Becker, ATPFinalsReachedSingles, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ATPFinalsReachedSingles Context triple: [Benjamin Becker, ATPFinalsReachedSingles, 4]
-
A.
grandSlamFinalistInSingles
Indicates that a person has reached the final round of a Grand Slam tennis tournament in singles competition.
-
B.
ATPsinglesTitles
Indicates the number of ATP-level singles titles a tennis player has won in professional tournaments.
-
C.
grandSlamSinglesFinalYear
Indicates the year in which a given Grand Slam singles final match took place.
-
D.
grandSlamSinglesFinalResult
Indicates the outcome of a Grand Slam tennis singles final match between competitors, typically specifying the winner, loser, and possibly the score.
-
E.
grandSlamSinglesFinalOpponent
Indicates that one person was the opposing player faced by another person in the final match of a Grand Slam singles tennis tournament.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fddafac819089cef4158f5e0ab5 |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:39 p.m.