Triple
T10488931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edinburgh derby |
E247362
|
entity |
| Predicate | derbyFocus |
P94577
|
FINISHED |
| Object | local bragging rights in Edinburgh |
—
|
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: local bragging rights in Edinburgh | Statement: [Edinburgh derby, derbyFocus, local bragging rights in Edinburgh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derbyFocus Context triple: [Edinburgh derby, derbyFocus, local bragging rights in Edinburgh]
-
A.
derby
Indicates a competitive match or contest, typically between closely linked or rival entities (such as teams from the same area or group).
-
B.
derbyInvolves
Indicates that a particular derby event includes or features the participation of a specified entity or entities.
-
C.
regionDerby
Indicates a competitive match or rivalry that takes place between teams or participants from the same geographic region.
-
D.
typeOfDerby
Indicates that one entity is a specific kind or category of derby in relation to another entity.
-
E.
derbyInLeagueSystem
Indicates that a derby (a match between local rivals) takes place within, and is organized as part of, a specific league system.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5097ca5c081908b47a08ca7885650 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d5092af880819082b42c0a68e45c5f |
completed | April 7, 2026, 1:39 p.m. |
Created at: April 6, 2026, 12:23 p.m.