Triple
T21456862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baz |
E529363
|
entity |
| Predicate | associatedWithBattingStyle |
P96341
|
FINISHED |
| Object | right-handed batsman |
—
|
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: right-handed batsman | Statement: [Baz, associatedWithBattingStyle, right-handed batsman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithBattingStyle Context triple: [Baz, associatedWithBattingStyle, right-handed batsman]
-
A.
associatedWithBattingStyleOfPerson
Indicates a relationship where something is connected to or characterized by the batting style of a specific person.
-
B.
battingStyleReputation
Indicates the commonly recognized characteristics or perceived quality of an entity’s batting style, as judged by observers or historical performance.
-
C.
battingType
chosen
Indicates the style or handedness with which a player bats (e.g., right-handed, left-handed, or both).
-
D.
associatedWithBowlingStyleOfPerson
Indicates a relationship where something is linked to or characterized by the specific bowling style used by a person.
-
E.
battingStrength
Indicates the relative power or effectiveness of an entity’s batting performance in a given 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9d7af248190a3bc06a390f390bf |
completed | April 23, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:08 p.m.