Triple
T35608525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SC Paderborn 07 |
E1028966
|
entity |
| Predicate | hasCoachHistorical |
P109234
|
FINISHED |
| Object | Steffen Baumgart |
E2210056
|
NE 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: Steffen Baumgart | Statement: [SC Paderborn 07, hasCoachHistorical, Steffen Baumgart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoachHistorical Context triple: [SC Paderborn 07, hasCoachHistorical, Steffen Baumgart]
-
A.
hasCoachedFor
Indicates that one entity has served in a coaching role for another entity, such as a team, organization, or individual.
-
B.
laterCoachedBy
Indicates that one entity was coached by another entity at a later time than some referenced coaching relationship or period.
-
C.
teamServedAsCoach
chosen
Indicates that a person held the role of coach for a particular team.
-
D.
hasCoachedIn
Indicates that one entity has served as a coach in a particular context, such as for a team, organization, event, or location.
-
E.
headCoachRecordIncludes
Indicates that a head coach’s record encompasses or contains a specified set of results, statistics, or achievements.
- F. None of above.
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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a5c44db1450819091bf2df603765bb8 |
completed | July 19, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.