Triple
T31141913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomasz Gollob |
E793808
|
entity |
| Predicate | rodeForClub |
P118445
|
FINISHED |
| Object | Polonia Bydgoszcz |
—
|
NE NERFINISHED |
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: Polonia Bydgoszcz | Statement: [Tomasz Gollob, rodeForClub, Polonia Bydgoszcz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rodeForClub Context triple: [Tomasz Gollob, rodeForClub, Polonia Bydgoszcz]
-
A.
rodeFor
chosen
Indicates that one entity traveled as a rider on behalf of, in service of, or representing another entity.
-
B.
privateClub
Indicates that an entity is a club or organization whose membership or access is restricted to selected or approved individuals rather than being open to the general public.
-
C.
mainClub2
Indicates that an entity serves as the primary or main club associated with another entity (such as a person, player, or organization).
-
D.
servesClub
Indicates that an entity provides service, work, or support to a particular club or organization.
-
E.
clubRebrandedAs
Indicates that a sports club has changed its official name or identity to become another specified club.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:06 p.m.