Triple
T35093548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hażlach |
E1012800
|
entity |
| Predicate | hasLocalSportsActivity |
P78147
|
FINISHED |
| Object | amateur 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: amateur football | Statement: [Hażlach, hasLocalSportsActivity, amateur football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalSportsActivity Context triple: [Hażlach, hasLocalSportsActivity, amateur football]
-
A.
hasLocalSport
chosen
Indicates that a place or community is associated with, supports, or regularly engages in a particular sport at the local level.
-
B.
hasSportingEvent
Indicates that a sporting event is associated with, held at, or organized by a given entity.
-
C.
hasLocalFootballGround
Indicates that a place or organization possesses or is associated with a nearby football ground used for local matches or activities.
-
D.
hasRecreationActivity
Indicates that an entity provides, includes, or is associated with a particular recreational activity.
-
E.
hasSportsOffered
Indicates that an entity provides or makes available certain sports as options or activities.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: May 3, 2026, 4:01 p.m.