Triple
T17389377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillside Stadium |
E422774
|
entity |
| Predicate | hasFieldSport |
P15165
|
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: [Hillside Stadium, hasFieldSport, association football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFieldSport Context triple: [Hillside Stadium, hasFieldSport, association football]
-
A.
hasSportsGround
Indicates that an entity possesses, includes, or is associated with a sports ground or athletic field as part of its facilities or area.
-
B.
includesSport
chosen
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
C.
hasSportingContext
Indicates that something is associated with, occurs within, or is relevant to a particular sporting or athletic context.
-
D.
hasAthletics
Indicates that an entity participates in, is associated with, or offers athletics-related activities or programs.
-
E.
hasMajorSport
Indicates that an entity is associated with or participates in a primary or most prominent 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a8c718c81909cb20749aaf12897 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.