Triple
T26099816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | England vs Australia |
E658365
|
entity |
| Predicate | homeGround2 |
P117330
|
FINISHED |
| Object | Sydney Cricket Ground |
—
|
NE NERFINISHED |
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: Sydney Cricket Ground | Statement: [England vs Australia, homeGround2, Sydney Cricket Ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeGround2 Context triple: [England vs Australia, homeGround2, Sydney Cricket Ground]
-
A.
homeGroundFrom
chosen
Indicates that an entity serves as the home ground or primary venue for another entity (such as a team or organization).
-
B.
homeGroundContext
Indicates the relationship between a sports team and the venue or location that serves as its primary home ground within a given contextual setting.
-
C.
homeGroundAlternateName
Indicates that an alternative or secondary name is used to refer to a particular home ground.
-
D.
homeGroundFeature
Indicates that a particular feature or characteristic is associated with or defines the home ground of an entity.
-
E.
homeGroundType
Indicates the type or category of venue that serves as an entity’s designated home ground.
- 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_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 7:54 p.m.