Triple
T36798600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GKS Jastrzębie |
E909257
|
entity |
| Predicate | associationFootballClubFromCountry |
P86066
|
FINISHED |
| Object | Poland |
E5029
|
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: Poland | Statement: [GKS Jastrzębie, associationFootballClubFromCountry, Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associationFootballClubFromCountry Context triple: [GKS Jastrzębie, associationFootballClubFromCountry, Poland]
-
A.
associationFootballClubIn
Indicates that an association football (soccer) club is located in or based in a specified place or region.
-
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.
associationFootballTeamOf
Indicates that one entity is the association football (soccer) team to which the other entity belongs or is affiliated.
-
D.
countryOfAssociatedClub
chosen
Indicates the country with which a given club is officially associated or based.
-
E.
associationFootballCode
Indicates that there is a specific code or rule set of association football that governs or characterizes the related entity.
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3dfac555388190a2d7df37c0c2db2c |
completed | June 26, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.