Triple
T22245036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | England–Scotland rugby union rivalry |
E549819
|
entity |
| Predicate | trophyFirstContested |
P38348
|
FINISHED |
| Object | 1879 |
—
|
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: 1879 | Statement: [England–Scotland rugby union rivalry, trophyFirstContested, 1879]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trophyFirstContested Context triple: [England–Scotland rugby union rivalry, trophyFirstContested, 1879]
-
A.
notableTrophyContested
Indicates that a competition or event is fought over a specific, distinguished trophy or award.
-
B.
trophyContestedBy
Indicates that a particular trophy is the object of competition among the specified participants or teams.
-
C.
firstContestedBetween
chosen
Indicates that a particular contest, dispute, or competition initially occurred between the specified entities.
-
D.
primaryChampionshipContested
Indicates that a competition or event involves the contesting of a primary or main championship title between participants.
-
E.
isFormerChampionshipTrophyOf
Indicates that an object previously served as the official championship trophy awarded for a particular competition or title.
- 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_69e11e41d9408190bd770cf282e22753 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f132170e5081909b9dbb204abf2a45 |
completed | April 28, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:38 p.m.