Triple
T6197187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canada national cricket team |
E138537
|
entity |
| Predicate | t20IStatusEffectiveFrom |
P66767
|
FINISHED |
| Object | 1 January 2019 |
—
|
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: 1 January 2019 | Statement: [Canada national cricket team, t20IStatusEffectiveFrom, 1 January 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: t20IStatusEffectiveFrom Context triple: [Canada national cricket team, t20IStatusEffectiveFrom, 1 January 2019]
-
A.
currentISOCodeEffectiveFrom
Indicates the date and time from which the current ISO code for an entity becomes valid or officially in effect.
-
B.
effectiveFor
Indicates that one entity successfully produces the intended effect, benefit, or desired outcome for another entity or condition.
-
C.
decisionEffectiveDate
chosen
Indicates the date on which a particular decision becomes valid, operative, or officially takes effect.
-
D.
statusAtTime
Indicates that an entity has a particular status or condition at a specified point in time.
-
E.
endDateOfficialUse
Indicates the date on which the official use or validity of something (such as a document, status, or authorization) comes to an end.
- 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_69c008ab9b3081908a11b2c744838435 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062508f5c8190a00291708a9a7de9 |
completed | March 22, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.