Triple
T21385461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mielec |
E527482
|
entity |
| Predicate | footballClubPlays |
P113953
|
FINISHED |
| Object | Polish football league system |
—
|
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: Polish football league system | Statement: [Mielec, footballClubPlays, Polish football league system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: footballClubPlays Context triple: [Mielec, footballClubPlays, Polish football league system]
-
A.
hostsFootballClub
Indicates that one entity serves as the home location or venue where a football club is based or plays its matches.
-
B.
associationFootballClub
Indicates that the subject is an association football (soccer) club, i.e., an organized team entity that plays the sport of association football.
-
C.
playsForClub
Indicates that a person is an active member of and participates in a particular sports club or team.
-
D.
teamPlaysIn
chosen
Indicates that a specific sports team participates or competes in a particular league, division, or competition.
-
E.
nearFootballClub
Indicates that one entity is located close to, or in the immediate vicinity of, a football 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_69e0b51f363c8190944000ab5523b02b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee62c9494081909efa74e189454dc6 |
completed | April 26, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:12 p.m.