Triple
T14174810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ba |
E351303
|
entity |
| Predicate | hasLocalTeamSport |
P78147
|
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: [Ba, hasLocalTeamSport, association football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalTeamSport Context triple: [Ba, hasLocalTeamSport, association 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.
hasSportsTeam
Indicates that an entity possesses, sponsors, or is represented by a sports team.
-
C.
containsSportsTeam
Indicates that one entity (typically a location or organization) has a sports team as part of it or within its boundaries.
-
D.
hasMajorSportsTeam
Indicates that a location is home to at least one prominent, officially recognized sports team, typically in a major professional or collegiate league.
-
E.
hasLocalFootballGround
Indicates that a place or organization possesses or is associated with a nearby football ground used for local matches 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b7cc3081909f4fa371e1eae130 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:02 a.m.