Triple
T31034893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calcutta Cup |
E790827
|
entity |
| Predicate | firstMatchPlayed |
P67594
|
FINISHED |
| Object | 10 March 1879 |
—
|
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: 10 March 1879 | Statement: [Calcutta Cup, firstMatchPlayed, 10 March 1879]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMatchPlayed Context triple: [Calcutta Cup, firstMatchPlayed, 10 March 1879]
-
A.
firstGamePlayed
Indicates the specific game that an entity participated in before any other, marking the earliest game in which it played.
-
B.
firstPlayed
Indicates that one entity was the earliest or initial thing (such as a song, game, or media item) that another entity engaged with or played.
-
C.
firstHomeMatchDate
Indicates the date on which an entity (such as a team) plays its first home match in a given context or season.
-
D.
firstMatchCompetition
Indicates that the referenced competition is the first one in which the entities faced each other or were matched against one another.
-
E.
firstOfficialMatchDate
chosen
Indicates the date on which an entity’s first official match or game was played.
- 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a036b0755888190a68a673664f0ea46 |
completed | May 12, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_6a036228676c8190aac9c90f7d8cedf7 |
completed | May 12, 2026, 5:23 p.m. |
Created at: April 29, 2026, 8:59 p.m.