Triple
T17125157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Finbarr’s GAA |
E415574
|
entity |
| Predicate | fieldedTeamsIn |
P96727
|
FINISHED |
| Object | Gaelic 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: Gaelic football | Statement: [St Finbarr’s GAA, fieldedTeamsIn, Gaelic football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldedTeamsIn Context triple: [St Finbarr’s GAA, fieldedTeamsIn, Gaelic football]
-
A.
fieldedCombinedTeamIn
Indicates that an entity organized and presented a joint or composite team to participate in a specified event or context.
-
B.
fieldedIn
Indicates that an entity was deployed, presented, or put into active use within a particular context, event, or domain.
-
C.
fieldsTeamsIn
chosen
Indicates that an entity organizes and sends a team to participate in a particular event, league, or competition.
-
D.
fielded
Indicates that an entity deployed, presented, or put forward another entity (such as a person, team, or resource) for participation or use in a particular context or activity.
-
E.
fieldsTeam
Indicates that an entity is a member of, or associated as part of, a particular team.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f025fce481908e261f2e363e14f9 |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.