Triple
T30741577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monaghan GAA |
E782702
|
entity |
| Predicate | fieldsTeamInCompetition |
P96727
|
FINISHED |
| Object | Ulster Senior Football Championship |
—
|
NE NERFINISHED |
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: Ulster Senior Football Championship | Statement: [Monaghan GAA, fieldsTeamInCompetition, Ulster Senior Football Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldsTeamInCompetition Context triple: [Monaghan GAA, fieldsTeamInCompetition, Ulster Senior Football Championship]
-
A.
fieldsTeamsIn
chosen
Indicates that an entity organizes and sends a team to participate in a particular event, league, or competition.
-
B.
fieldsTeam
Indicates that an entity is a member of, or associated as part of, a particular team.
-
C.
featuresTeams
Indicates that something prominently presents or includes specific teams as a central element or focus.
-
D.
leagueTeam
Indicates that a team is a member or participant of a particular league.
-
E.
teamLineup
Indicates the assignment and ordering of participants or members that make up a specific team configuration for an event or activity.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 29, 2026, 8:38 p.m.