Triple
T33014516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramelton |
E844736
|
entity |
| Predicate | localSports |
P78147
|
FINISHED |
| Object | Gaelic games |
—
|
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: Gaelic games | Statement: [Ramelton, localSports, Gaelic games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localSports Context triple: [Ramelton, localSports, Gaelic games]
-
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.
localCompetition
Indicates that two entities are competing with each other within the same local or geographically limited market or area.
-
C.
sportsDistrict
Indicates that a district is associated with or designated for sports-related activities, facilities, or organizations.
-
D.
sportsGround
Indicates that a location functions as a sports ground, i.e., a place designated or used for playing sports or athletic activities.
-
E.
countrySportsContext
Indicates the relationship between a country and the sports, sporting culture, or sports-related context associated with it.
- 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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:23 a.m.