Triple
T28068196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glasgow derby |
E709314
|
entity |
| Predicate | firstContestedYear |
P200785
|
FINISHED |
| Object | 1888 |
—
|
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: 1888 | Statement: [Glasgow derby, firstContestedYear, 1888]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstContestedYear Context triple: [Glasgow derby, firstContestedYear, 1888]
-
A.
firstContestedBetween
Indicates that a particular contest, dispute, or competition initially occurred between the specified entities.
-
B.
firstContestedIn
Indicates the event, competition, or context in which something (such as a title, office, or position) was initially challenged or competed for.
-
C.
firstSeasonContested
Indicates the season in which an entity (such as a team, player, or participant) first took part in a particular competition or contest.
-
D.
firstElectionYear
Indicates the calendar year in which an entity (such as a person, office, or political body) first participated in or was subject to an election.
-
E.
wasContestedBetween
Indicates that an event, position, or resource was the subject of competition or dispute involving two or more opposing parties.
- F. None of above. chosen
Provenance (4 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
| PDg | Predicate description generation | batch_69ffacdea2408190949dba9edeca4412 |
completed | May 9, 2026, 9:53 p.m. |
Created at: April 27, 2026, 8:44 p.m.