Triple
T26099810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | England vs Australia |
E658365
|
entity |
| Predicate | firstTestMatchLocation |
P97342
|
FINISHED |
| Object | Melbourne 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: Melbourne Cricket Ground | Statement: [England vs Australia, firstTestMatchLocation, Melbourne Cricket Ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstTestMatchLocation Context triple: [England vs Australia, firstTestMatchLocation, Melbourne Cricket Ground]
-
A.
testLocation
Indicates the place or environment where a test, examination, or experimental procedure is conducted.
-
B.
firstTestMatchDate
Indicates the date on which an entity (such as a team or player) participated in its first Test match.
-
C.
firstTestVenue
chosen
Indicates the venue where something (such as an event, performance, or test) was held or conducted for the first time.
-
D.
firstLocation
Indicates the initial or primary place where an entity is situated, originates, or where an event or relationship begins.
-
E.
firstFirstClassMatch
Indicates that the referenced match is the earliest (chronologically first) match classified as a first-class match for the given context or entity.
- 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_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: April 26, 2026, 7:54 p.m.