Triple
T759367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olaf Kölzig |
E16030
|
entity |
| Predicate | shootsOrCatches |
P17665
|
FINISHED |
| Object | left |
—
|
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 | Statement: [Olaf Kölzig, shootsOrCatches, left]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shootsOrCatches Context triple: [Olaf Kölzig, shootsOrCatches, left]
-
A.
shoots
Indicates that one entity propels a projectile or discharge toward another entity, typically with the intent to hit or affect it.
-
B.
catches
Indicates that one entity successfully seizes, intercepts, or takes hold of another entity, often stopping its motion or preventing its escape.
-
C.
shootingStyle
chosen
Indicates the characteristic manner or technique with which an entity performs a shooting action (e.g., in sports or photography).
-
D.
captures
Indicates that one entity seizes, traps, or takes control of another entity, often preventing its escape or freedom.
-
E.
capturedEquipment
Indicates that one party has taken possession of another party’s equipment, typically as a result of conflict, competition, or enforcement.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a67f9778819098d3c144dd26b976 |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a50348088190873a1446db657a78 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.