Triple
T27455658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klaus Fischer |
E692583
|
entity |
| Predicate | notableGoalType |
P201138
|
FINISHED |
| Object | bicycle kick |
—
|
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: bicycle kick | Statement: [Klaus Fischer, notableGoalType, bicycle kick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGoalType Context triple: [Klaus Fischer, notableGoalType, bicycle kick]
-
A.
scoredNotableGoal
Indicates that an entity achieved a particularly important or memorable goal in a game or competitive context.
-
B.
notableOutcomeType
Indicates that a relationship exists where an outcome is characterized as being of a particular notable or significant type.
-
C.
notableWinType
Indicates that the relationship specifies the particular category or type of a notable victory associated with an entity.
-
D.
notableObjective
Indicates that an entity has a significant, distinguished, or widely recognized goal, purpose, or target associated with it.
-
E.
notableOutcome
Indicates that an action, event, or entity leads to or is associated with a significant, noteworthy result or consequence.
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69ffcc6182b48190afb598ced6500e66 |
completed | May 10, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69ffcbb363748190bc6f8d038fba44ff |
completed | May 10, 2026, 12:05 a.m. |
| PDg | Predicate description generation | batch_69ffcc60dae48190b76b3eb7e2ce5103 |
completed | May 10, 2026, 12:08 a.m. |
Created at: April 27, 2026, 12:48 p.m.