Triple
T26099606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedser Stand |
E658358
|
entity |
| Predicate | tenantVenueFor |
P53622
|
FINISHED |
| Object | England cricket team home matches at The Oval |
—
|
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: England cricket team home matches at The Oval | Statement: [Bedser Stand, tenantVenueFor, England cricket team home matches at The Oval]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tenantVenueFor Context triple: [Bedser Stand, tenantVenueFor, England cricket team home matches at The Oval]
-
A.
hostVenueInstanceOf
Indicates that a specific host venue is an instance or concrete realization of a more general venue type or category.
-
B.
hostsVenue
Indicates that an entity provides or manages a location where an event or activity takes place.
-
C.
usesVenues
Indicates that one entity makes use of or operates within specific venues or locations to carry out its activities or services.
-
D.
homeVenueAlsoUsedBy
chosen
Indicates that the venue serving as a home location for one entity is also used as a venue by another entity.
-
E.
homeVenueOwned
Indicates that the specified home venue is legally owned or possessed by the associated entity.
- 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_69f607394b6881909bcf1a6871359541 |
completed | May 2, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 7:53 p.m.