Triple
T34101679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cricket Green, Mitcham |
E874586
|
entity |
| Predicate | hasCricketClubTenant |
P191382
|
FINISHED |
| Object | Mitcham Cricket Club |
—
|
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: Mitcham Cricket Club | Statement: [Cricket Green, Mitcham, hasCricketClubTenant, Mitcham Cricket Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCricketClubTenant Context triple: [Cricket Green, Mitcham, hasCricketClubTenant, Mitcham Cricket Club]
-
A.
hasCricketGround
Indicates that one entity possesses, contains, or includes a cricket ground as part of its facilities or attributes.
-
B.
hasCountyCricketClub
Indicates that a place or administrative region possesses or is home to a county-level cricket club.
-
C.
hasSharedCricketTeam
Indicates that two or more entities jointly support, own, or are represented by the same cricket team.
-
D.
hasHomeClub
Indicates that an entity (typically a person, such as an athlete) is associated with a particular club as their primary or official home organization.
-
E.
tenantClubLeague
Indicates that a club participates as a tenant (home user of facilities) in a particular league.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: May 1, 2026, 1:53 a.m.