Triple
T34514336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-Ireland Senior Hurling Championship Final |
E886106
|
entity |
| Predicate | hasPreMatchParade |
P56123
|
FINISHED |
| Object | team parade with bands |
—
|
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: team parade with bands | Statement: [All-Ireland Senior Hurling Championship Final, hasPreMatchParade, team parade with bands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreMatchParade Context triple: [All-Ireland Senior Hurling Championship Final, hasPreMatchParade, team parade with bands]
-
A.
hasAthletesParade
Indicates that a group or organization holds or organizes a parade featuring its athletes.
-
B.
hasParadeFeature
chosen
Indicates that an entity includes, exhibits, or is characterized by a particular feature or element of a parade.
-
C.
hasParades
Indicates that an entity regularly holds or hosts parades as events or activities.
-
D.
hasParadeRoute
Indicates that an entity is associated with or follows a specific route used for a parade.
-
E.
hadPreShowMatch
Indicates that one entity participated in or was involved with a match that took place before the main show or primary event.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0311c202408190be88a85337aacf11 |
completed | May 12, 2026, 11:40 a.m. |
| PD | Predicate disambiguation | batch_6a0310b0c9c88190ab218d47d4f432ed |
completed | May 12, 2026, 11:36 a.m. |
Created at: May 1, 2026, 2:01 a.m.