Triple
T22074359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irani Cup |
E545485
|
entity |
| Predicate | traditionalTiming |
P15545
|
FINISHED |
| Object | start of Indian domestic season |
—
|
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: start of Indian domestic season | Statement: [Irani Cup, traditionalTiming, start of Indian domestic season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalTiming Context triple: [Irani Cup, traditionalTiming, start of Indian domestic season]
-
A.
timingMethod
Indicates the method or technique used to measure or record the timing of an event or process.
-
B.
timingStandard
Indicates that one entity specifies or conforms to the timing rules, constraints, or reference schedule defined by another entity.
-
C.
traditionalStart
chosen
Indicates that an event, process, or sequence begins in the customary or historically established way.
-
D.
requiresTiming
Indicates that one entity’s occurrence, execution, or validity depends on being coordinated with a specific time or temporal condition related to another entity.
-
E.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1288affb081908b64742f7bf467fa |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.