Triple
T29133206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tim Henman |
E738435
|
entity |
| Predicate | grandSlamBestResultWimbledonSinglesYears |
P167948
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Tim Henman, grandSlamBestResultWimbledonSinglesYears, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grandSlamBestResultWimbledonSinglesYears Context triple: [Tim Henman, grandSlamBestResultWimbledonSinglesYears, 1998]
-
A.
grandSlamBestResultWimbledon
Indicates the best performance or highest round an entity has achieved at the Wimbledon tennis championships.
-
B.
wonWimbledonSingles
Indicates that an entity has won the Wimbledon tennis tournament in the singles category.
-
C.
WimbledonSinglesFinals
Indicates that the entities are participants in the singles final match of the Wimbledon tennis tournament.
-
D.
grandSlamBestResultAustralianOpen
Indicates the best performance or highest round an entity has achieved specifically at the Australian Open in Grand Slam competition.
-
E.
grandSlamSinglesFinalYear
Indicates the year in which a given Grand Slam singles final match took place.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66e5f7e30819094530abceabd5f43 |
completed | May 2, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66d75a8788190aa9ca2c977429045 |
completed | May 2, 2026, 9:32 p.m. |
Created at: April 28, 2026, 11:33 a.m.