Triple
T14451882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himachal Pradesh Cricket Association Stadium |
E358356
|
entity |
| Predicate | firstTestMatchDate |
P114332
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Himachal Pradesh Cricket Association Stadium, firstTestMatchDate, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstTestMatchDate Context triple: [Himachal Pradesh Cricket Association Stadium, firstTestMatchDate, 2017]
-
A.
firstRoundDate
Indicates the date on which the first round of an event, process, or competition takes place.
-
B.
firstMLSMatchDate
Indicates the calendar date on which an entity (typically a player or team) participated in its first official Major League Soccer (MLS) match.
-
C.
firstOfficialMatchDate
Indicates the date on which an entity’s first official match or game was played.
-
D.
firstHomeMatchDate
Indicates the date on which an entity (such as a team) plays its first home match in a given context or season.
-
E.
finalMatchDate
Indicates the calendar date on which the final or deciding match in a series, tournament, or competition takes place.
- F. None of above. chosen
Provenance (4 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de916244948190bb09d1bfc485ba50 |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:19 a.m.