Triple
T2980770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gordon Reid |
E80503
|
entity |
| Predicate | playsBackhand |
P44417
|
FINISHED |
| Object | one-handed backhand |
—
|
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: one-handed backhand | Statement: [Gordon Reid, playsBackhand, one-handed backhand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsBackhand Context triple: [Gordon Reid, playsBackhand, one-handed backhand]
-
A.
opponentInComeback
Indicates that an entity serves as the opposing side or competitor in a situation characterized as a comeback (e.g., recovering from a disadvantage).
-
B.
eraPlayed
Indicates the historical or stylistic time period during which something (typically a work or performance) was played or took place.
-
C.
usesBatAndBall
Indicates that the action or activity involves the use of both a bat and a ball together.
-
D.
battedBehind
Indicates that one participant took their turn to bat after another participant in a batting order.
-
E.
playedWithout
Indicates that one participant engaged in a play-related activity while another expected or relevant participant was absent or not involved.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad999e91788190a2d430dd0600a660 |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:58 p.m.