Triple
T26099718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pavilion End |
E658362
|
entity |
| Predicate | homeGroundEndOf |
P113386
|
FINISHED |
| Object | Surrey County 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: Surrey County Cricket Club | Statement: [Pavilion End, homeGroundEndOf, Surrey County Cricket Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeGroundEndOf Context triple: [Pavilion End, homeGroundEndOf, Surrey County Cricket Club]
-
A.
homeGroundFrom
Indicates that an entity serves as the home ground or primary venue for another entity (such as a team or organization).
-
B.
homeEndInStadium
Indicates that a team's home games are played in a particular stadium.
-
C.
homeGroundContext
Indicates the relationship between a sports team and the venue or location that serves as its primary home ground within a given contextual setting.
-
D.
homeEndLocation
Indicates the location where a journey, route, or movement that starts from home comes to an end.
-
E.
laterHomeGround
chosen
Indicates that one entity became the home ground of the other at a later time, after some previous home ground or earlier period.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6073a39408190994ac1c8983a7c0b |
completed | May 2, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:54 p.m.