Triple
T31505917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wisła Płock |
E803815
|
entity |
| Predicate | associationFootballTeam |
P207443
|
FINISHED |
| Object | Wisła Płock first team |
—
|
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: Wisła Płock first team | Statement: [Wisła Płock, associationFootballTeam, Wisła Płock first team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associationFootballTeam Context triple: [Wisła Płock, associationFootballTeam, Wisła Płock first team]
-
A.
associationFootballClub
Indicates that the subject is an association football (soccer) club, i.e., an organized team entity that plays the sport of association football.
-
B.
associationFootballTeamOf
Indicates that one entity is the association football (soccer) team to which the other entity belongs or is affiliated.
-
C.
associationFootballClubIn
Indicates that an association football (soccer) club is located in or based in a specified place or region.
-
D.
hostsFootballClub
Indicates that one entity serves as the home location or venue where a football club is based or plays its matches.
-
E.
foundedFootballClub
Indicates that a person or entity established or created a particular football club.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 30, 2026, 9:47 p.m.