Triple
T6862910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The G |
E158325
|
entity |
| Predicate | appliesToVenueType |
P10640
|
FINISHED |
| Object | cricket ground |
—
|
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: cricket ground | Statement: [The G, appliesToVenueType, cricket ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToVenueType Context triple: [The G, appliesToVenueType, cricket ground]
-
A.
refersToVenueType
chosen
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
B.
isRegularVenueFor
Indicates that a location is commonly or routinely used as the venue for a particular event, activity, or entity’s gatherings.
-
C.
servesVenue
Indicates that an entity provides services or functions in support of a particular venue.
-
D.
hasPrincipalVenue
Indicates that an entity has a primary or main venue where its activities, events, or operations predominantly take place.
-
E.
connectsToEventVenue
Indicates that one entity serves as a link or route providing access or connection to an event 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_69c68830cdbc8190a8301c7a9d9f651a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6da3ce95081909a424ac04bc7fa07 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b168908190b2f7c724b1bc7fc9 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:21 p.m.