Triple
T23864224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durham County Cricket Club |
E592531
|
entity |
| Predicate | homeGroundNameVariant |
P129911
|
FINISHED |
| Object | Emirates Riverside |
—
|
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: Emirates Riverside | Statement: [Durham County Cricket Club, homeGroundNameVariant, Emirates Riverside]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeGroundNameVariant Context triple: [Durham County Cricket Club, homeGroundNameVariant, Emirates Riverside]
-
A.
homeGroundAlternateName
chosen
Indicates that an alternative or secondary name is used to refer to a particular home ground.
-
B.
primaryHomeGroundNot
Indicates that the specified location is explicitly not the entity’s primary home ground.
-
C.
homeGroundNameHistory
Indicates the historical sequence of names that have been used for an entity’s home ground or home venue over time.
-
D.
homeFieldNamedAfter
Indicates that one entity’s home playing field bears the name of another entity.
-
E.
homeGroundFrom
Indicates that an entity serves as the home ground or primary venue for another entity (such as a team or organization).
- 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cae22ff08190b7085cae21938bb4 |
completed | April 29, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:13 p.m.