Triple
T11238904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Blake |
E266017
|
entity |
| Predicate | capturedTitle |
P12204
|
FINISHED |
| Object | 2006 ATP Tour Championships runner-up in singles |
—
|
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: 2006 ATP Tour Championships runner-up in singles | Statement: [James Blake, capturedTitle, 2006 ATP Tour Championships runner-up in singles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capturedTitle Context triple: [James Blake, capturedTitle, 2006 ATP Tour Championships runner-up in singles]
-
A.
aimedTitle
Indicates that one entity is the intended or targeted title or heading associated with another entity.
-
B.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
C.
receivedTitle
chosen
Indicates that an entity has been formally granted or awarded a specific title or honor.
-
D.
titles
Indicates that one entity holds a formal title, designation, or name associated with another entity.
-
E.
battedTitle
Indicates that one entity served as the title or headline for another entity in a way that was prominently featured or “batted” (highlighted) in a media or publication context.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e918375081908c2a7ccb50cbf331 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d7878906f48190b63ddc103a0c8f9b |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:30 p.m.