Triple
T36350139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munster Senior Cup |
E895178
|
entity |
| Predicate | primaryParticipantsFrom |
P204834
|
FINISHED |
| Object | Munster |
E61441
|
NE 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: Munster | Statement: [Munster Senior Cup, primaryParticipantsFrom, Munster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryParticipantsFrom Context triple: [Munster Senior Cup, primaryParticipantsFrom, Munster]
-
A.
primaryParticipant
Indicates that an entity plays the main or most central role in a given event, activity, or relationship.
-
B.
primaryPeople
Indicates that the referenced people are the main or most important individuals associated with a given entity, event, or context.
-
C.
secondaryParticipants
Indicates that certain entities participate in an event or activity in a supporting or non-primary role alongside the main participants.
-
D.
originalParticipantsType
Indicates the type or category of participants that were initially involved in an event, action, or relationship.
-
E.
primaryMembers
Indicates that the related entities are the main or most important members within a larger group or organization.
- F. None of above. chosen
Provenance (5 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39cfbb966c8190ab9a83f79964d691 |
completed | June 23, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:09 p.m.