Triple
T31573374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadion Miejski w Białymstoku |
E805624
|
entity |
| Predicate | usesForSport |
P45944
|
FINISHED |
| Object | association football |
—
|
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: association football | Statement: [Stadion Miejski w Białymstoku, usesForSport, association football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesForSport Context triple: [Stadion Miejski w Białymstoku, usesForSport, association football]
-
A.
usedSportFor
Indicates that an entity employs or utilizes a particular sport as a means, tool, or context for achieving some purpose or performing an activity.
-
B.
usedInSport
Indicates that something (such as an object, technique, or concept) is employed or utilized within the context of a particular sport.
-
C.
alsoUsedForSport
chosen
Indicates that something primarily associated with one purpose is additionally used for sporting activities or athletic purposes.
-
D.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
E.
usesBallSport
Indicates that an activity or event involves the use of a ball as part of a sport.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 30, 2026, 10:20 p.m.