Triple
T23213391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorking F.C. |
E580663
|
entity |
| Predicate | hasLocalDerbiesWith |
P18267
|
FINISHED |
| Object | nearby sides |
—
|
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: nearby sides | Statement: [Dorking F.C., hasLocalDerbiesWith, nearby sides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalDerbiesWith Context triple: [Dorking F.C., hasLocalDerbiesWith, nearby sides]
-
A.
hasHomeDerbyFor
Indicates that one entity serves as the home venue or location where another entity’s derby event is held.
-
B.
hasLocalRivalry
chosen
Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
-
C.
hasLocalRivalryVenueWith
Indicates that two entities share a venue or location where a local rivalry between them is regularly contested or expressed.
-
D.
hasLocalSport
Indicates that a place or community is associated with, supports, or regularly engages in a particular sport at the local level.
-
E.
hasHomeStadiumInDerby
Indicates that an entity’s home stadium is located in the city or area of Derby.
- 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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f19162c77c8190ba29c59ea9695316 |
completed | April 29, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:07 p.m.