Triple
T31141917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomasz Gollob |
E793808
|
entity |
| Predicate | rodeInLeague |
P171191
|
FINISHED |
| Object | Polish Ekstraliga |
—
|
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: Polish Ekstraliga | Statement: [Tomasz Gollob, rodeInLeague, Polish Ekstraliga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rodeInLeague Context triple: [Tomasz Gollob, rodeInLeague, Polish Ekstraliga]
-
A.
usedInLeague
Indicates that an entity (such as a team, player, or item) participates or is employed within a particular league.
-
B.
foldedInLeague
Indicates that a sports team or organization has ceased operations and been absorbed or discontinued within a particular league.
-
C.
competitiveLeague
Indicates that the entities participate in the same organized competition or league where they compete against each other.
-
D.
continuedInLeague
Indicates that an entity remained participating in the same league across consecutive seasons or time periods.
-
E.
managedInLeague
Indicates that an entity served as a manager or head coach for a team participating in a specified league.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c6f01e881908fa84f5d429d37ae |
completed | May 3, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f69c2127088190ae92c72461576d3b |
completed | May 3, 2026, 12:51 a.m. |
Created at: April 29, 2026, 9:06 p.m.