Triple
T6077953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mansfield Town F.C. |
E135447
|
entity |
| Predicate | localDerbyType |
P52081
|
FINISHED |
| Object | Nottinghamshire derbies |
—
|
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: Nottinghamshire derbies | Statement: [Mansfield Town F.C., localDerbyType, Nottinghamshire derbies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localDerbyType Context triple: [Mansfield Town F.C., localDerbyType, Nottinghamshire derbies]
-
A.
regionDerby
chosen
Indicates a competitive match or rivalry that takes place between teams or participants from the same geographic region.
-
B.
cityDerby
Indicates a competitive or rivalry relationship between two cities, often in sports or similar local contests.
-
C.
playsInDerby
Indicates participation by an entity as a competitor or performer in a derby event.
-
D.
derby
Indicates a competitive match or contest, typically between closely linked or rival entities (such as teams from the same area or group).
-
E.
hasDerbyStatus
Indicates that an entity holds a specific status or classification related to a derby event or competition.
- 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_69c0087ad31c8190ab936e0ff28614b6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c057706d9881909b52093282593886 |
completed | March 22, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c049f21fe08190995df3c5c05fb8ea |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:11 p.m.