Triple
T2985588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Károly Takács |
E80616
|
entity |
| Predicate | handednessAfterInjury |
P44483
|
FINISHED |
| Object | left-handed |
—
|
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: left-handed | Statement: [Károly Takács, handednessAfterInjury, left-handed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handednessAfterInjury Context triple: [Károly Takács, handednessAfterInjury, left-handed]
-
A.
handedness
Indicates the preference or dominance of one hand over the other in performing actions or tasks.
-
B.
involvedArm
Indicates that a particular arm, branch, or subdivision of an organization or entity participates in or is implicated in a specified event, activity, or relationship.
-
C.
rightHandedComponent
Indicates that one entity functions as the right-handed component or counterpart within a paired or bilateral relationship to another entity.
-
D.
hemisphereDominance
Indicates which brain hemisphere (left or right) is functionally dominant for a given cognitive or neural process in an entity.
-
E.
battingHand
Indicates the handedness a player uses when batting, such as right-handed, left-handed, or switch.
- 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c76dfc8190b08bd6110ffabf25 |
completed | March 8, 2026, 3:46 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:59 p.m.