Triple
T4573628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australia national cricket team |
E123092
|
entity |
| Predicate | t20iStatusSince |
P19818
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [Australia national cricket team, t20iStatusSince, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: t20iStatusSince Context triple: [Australia national cricket team, t20iStatusSince, 2005]
-
A.
t20IStatus
Indicates the status or classification of an entity specifically in the context of Twenty20 International (T20I) cricket.
-
B.
currentStatusSince
chosen
Indicates the point in time since which an entity has held its current status or state.
-
C.
continuityStatus
Indicates the state of whether something continues without interruption or has been broken, paused, or reset over time.
-
D.
trainingStatus
Indicates the current state or phase of an entity within a training or learning process.
-
E.
maintenanceStatus
Indicates the current state or condition of an entity with respect to its maintenance activities, such as whether it is pending, in progress, completed, or overdue.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c89a5c81909a78bf0ac64777ad |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.