Triple
T38327323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northampton County Ground |
E1036822
|
entity |
| Predicate | openedAsCricketGround |
P26419
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Northampton County Ground, openedAsCricketGround, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsCricketGround Context triple: [Northampton County Ground, openedAsCricketGround, 19th century]
-
A.
hasCricketGround
Indicates that one entity possesses, contains, or includes a cricket ground as part of its facilities or attributes.
-
B.
typeOfCricket
Indicates that one entity is a specific kind or category of cricket in relation to another entity.
-
C.
servesCricketGround
Indicates that one entity functions as the home or host venue for cricket matches or activities for another entity.
-
D.
coHostCricketBoard
Indicates a relationship where one entity jointly hosts or organizes a cricket board or cricket-related governing body together with another entity.
-
E.
openedAsSportsVenue
chosen
Indicates that a place or facility began its operation specifically for hosting sports events or activities.
- 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 3, 2026, 4:30 p.m.