Triple
T23528029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forest–Derby rivalry |
E576485
|
entity |
| Predicate | hasDerbyName |
P153117
|
FINISHED |
| Object | East Midlands derby |
—
|
NE NERFINISHED |
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: East Midlands derby | Statement: [Forest–Derby rivalry, hasDerbyName, East Midlands derby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDerbyName Context triple: [Forest–Derby rivalry, hasDerbyName, East Midlands derby]
-
A.
isDerby
Indicates that a competition or match is a derby, typically involving teams or participants from the same locality or with a strong rivalry.
-
B.
hasDerbyStatus
Indicates that an entity holds a specific status or classification related to a derby event or competition.
-
C.
hasDerbyColor
Indicates that one entity (typically a derby or race event) is associated with a specific color used to represent or identify it.
-
D.
hasHomeDerbyFor
Indicates that one entity serves as the home venue or location where another entity’s derby event is held.
-
E.
isFromCityWithDerby
Indicates that an entity originates from a city that has a football (or sports) derby with another team from the same city.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac758038819098f5f597be39274e |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:09 p.m.