Triple
T31424214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sweden and Denmark |
E801614
|
entity |
| Predicate | sharesSportRivalry |
P103538
|
FINISHED |
| Object | football rivalry |
—
|
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: football rivalry | Statement: [Sweden and Denmark, sharesSportRivalry, football rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesSportRivalry Context triple: [Sweden and Denmark, sharesSportRivalry, football rivalry]
-
A.
sportsRival
chosen
Indicates a competitive adversarial relationship between two sports teams, players, or organizations, typically characterized by recurring contests and heightened mutual opposition.
-
B.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
C.
rivalLeague
Indicates that two leagues are in competition with each other, typically vying for similar audiences, resources, or status.
-
D.
rivalryFocus
Indicates a relationship in which one entity is the primary target or center of another entity’s competitive or adversarial rivalry.
-
E.
divisionRivalry
Indicates a competitive or adversarial relationship between entities that belong to the same division or subgroup within a larger organization or system.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
Created at: April 30, 2026, 8:51 p.m.