Triple
T20755282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herbert Sutcliffe |
E510827
|
entity |
| Predicate | battingTrait |
P132620
|
FINISHED |
| Object | high level of concentration |
—
|
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: high level of concentration | Statement: [Herbert Sutcliffe, battingTrait, high level of concentration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battingTrait Context triple: [Herbert Sutcliffe, battingTrait, high level of concentration]
-
A.
battingStrength
Indicates the relative power or effectiveness of an entity’s batting performance in a given context.
-
B.
battingType
Indicates the style or handedness with which a player bats (e.g., right-handed, left-handed, or both).
-
C.
battingAverageType
Indicates the type or category of a batting average associated with a player or performance (e.g., season, career, situational).
-
D.
battingStyleReputation
chosen
Indicates the commonly recognized characteristics or perceived quality of an entity’s batting style, as judged by observers or historical performance.
-
E.
battingAverage
Indicates the statistical relationship between a batter’s number of hits and official at-bats, expressing how often they successfully get a hit.
- 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c22e0d288190ba924423af59d70d |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:34 p.m.