Triple
T18913039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newlands Cricket Ground |
E462651
|
entity |
| Predicate | isHistoricVenue |
P121187
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Newlands Cricket Ground, isHistoricVenue, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricVenue Context triple: [Newlands Cricket Ground, isHistoricVenue, yes]
-
A.
historicalVenue
chosen
Indicates that a location serves or has served as the site where a historically significant event or activity took place.
-
B.
operatedHistoricVenue
Indicates that an entity managed or ran a venue of historical significance during some period in the past.
-
C.
legacyVenue
Indicates that a venue has historical or long-standing significance, often preserved or recognized due to its past importance or enduring role.
-
D.
historicalVenuePattern
Indicates a recurring or characteristic way in which venues are used, configured, or associated within historical contexts or periods.
-
E.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c624516c81909e6bf04707d3c71c |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.