Triple
T14369144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Stand |
E356312
|
entity |
| Predicate | venueTypeServed |
P48322
|
FINISHED |
| Object | international cricket venue |
—
|
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: international cricket venue | Statement: [South Stand, venueTypeServed, international cricket venue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venueTypeServed Context triple: [South Stand, venueTypeServed, international cricket venue]
-
A.
servesVenue
Indicates that an entity provides services or functions in support of a particular venue.
-
B.
servesType
chosen
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
C.
venueTypeOperated
Indicates that an entity operates or manages a venue of a specified type.
-
D.
isTypicallyServedFor
Indicates that one item is most commonly or customarily served as a meal or course for the other (e.g., a dish typically served for breakfast, lunch, or dinner).
-
E.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8fb0b8988190ab834a85911c015c |
completed | April 14, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:15 a.m.