Triple
T22146608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vijay Hazare Trophy |
E547302
|
entity |
| Predicate | formatChangeability |
P46363
|
FINISHED |
| Object | tournament format has varied over seasons |
—
|
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: tournament format has varied over seasons | Statement: [Vijay Hazare Trophy, formatChangeability, tournament format has varied over seasons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatChangeability Context triple: [Vijay Hazare Trophy, formatChangeability, tournament format has varied over seasons]
-
A.
formatMayChange
chosen
Indicates that the format or structure of something is subject to modification and may not remain consistent over time.
-
B.
changeType
Indicates the specific kind or category of modification that has occurred to an entity or relationship.
-
C.
changeDescription
Indicates that an entity’s descriptive information has been modified from a previous state.
-
D.
cannotChange
Indicates that an entity is unable or not permitted to alter the state, value, or properties of another entity or relationship.
-
E.
changesProperty
Indicates that one entity causes a change in a specific property or attribute of another 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f097248190a8a3cdff1593b5b5 |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.