Triple
T4180522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irish Cup |
E86582
|
entity |
| Predicate | notableRivalryContext |
P893
|
FINISHED |
| Object | Linfield F.C. vs Glentoran F.C. |
—
|
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: Linfield F.C. vs Glentoran F.C. | Statement: [Irish Cup, notableRivalryContext, Linfield F.C. vs Glentoran F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRivalryContext Context triple: [Irish Cup, notableRivalryContext, Linfield F.C. vs Glentoran F.C.]
-
A.
notableRivalry
chosen
Indicates a significant, well-recognized competitive or adversarial relationship between two entities.
-
B.
notableRivalTeam
Indicates that one team is recognized as a significant or well-known rival of another team.
-
C.
conferenceRivalry
Indicates a competitive or adversarial relationship between entities that belong to the same conference or organized grouping.
-
D.
notableMatch
Indicates that there exists a particularly significant or noteworthy match or pairing between the related entities.
-
E.
notablePlayoffContext
Indicates that an event, performance, or situation occurred within a playoff setting and is significant or noteworthy in that postseason context.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.