Triple
T31034915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calcutta Cup |
E790827
|
entity |
| Predicate | competitionResultRule |
P159485
|
FINISHED |
| Object | holder retains cup in event of a draw |
—
|
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: holder retains cup in event of a draw | Statement: [Calcutta Cup, competitionResultRule, holder retains cup in event of a draw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionResultRule Context triple: [Calcutta Cup, competitionResultRule, holder retains cup in event of a draw]
-
A.
competitionResult
Indicates the outcome of a competitive event, specifying how participants placed or performed relative to one another.
-
B.
contestRule
Indicates that there is a rule or regulation governing how a contest is conducted or participated in.
-
C.
matchOutcomeRule
chosen
Indicates the rule or condition that determines the outcome of a match between participants.
-
D.
competitionEnd
Indicates that a competitive event or contest has concluded or reached its final state.
-
E.
competitionSystem
Indicates the structured set of rules, formats, and procedures that govern how a competition is organized, conducted, and decided.
- 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_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 8:59 p.m.