Triple
T3943797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulster Cup |
E92095
|
entity |
| Predicate | tournamentScope |
P15208
|
FINISHED |
| Object | regional |
—
|
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: regional | Statement: [Ulster Cup, tournamentScope, regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentScope Context triple: [Ulster Cup, tournamentScope, regional]
-
A.
tournamentPhaseCoverage
Indicates the specific stage or phase of a tournament that an action, event, or data item pertains to or covers.
-
B.
otherTournament
Indicates a relationship where one tournament is distinct from and not the same as another tournament.
-
C.
competitionStage
Indicates the specific phase or round within a broader competition in which the related entities participate or are situated.
-
D.
hasCompetitionScope
chosen
Indicates the extent or boundaries within which a competition, contest, or competitive activity is defined or applies.
-
E.
rivalryTournament
Indicates a competitive relationship where entities repeatedly oppose each other in a structured tournament setting, emphasizing ongoing rivalry.
- 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee764235081909309b3c982f322a9 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.