Triple
T31455764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australia women's national cricket team |
E802444
|
entity |
| Predicate | rivalryNamed |
P2578
|
FINISHED |
| Object | Women's Ashes |
—
|
NE NERFINISHED |
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: Women's Ashes | Statement: [Australia women's national cricket team, rivalryNamed, Women's Ashes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryNamed Context triple: [Australia women's national cricket team, rivalryNamed, Women's Ashes]
-
A.
rivalryName
chosen
Indicates that a specific name or label is assigned to a rivalry relationship between two entities.
-
B.
rivalryNamedAfter
Indicates that a rivalry between entities is named after a particular person, place, event, or concept.
-
C.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
D.
rivalryCharacterizedBy
Indicates a relationship where a rivalry is defined or distinguished by a particular feature, quality, or circumstance.
-
E.
rivalryFocus
Indicates a relationship in which one entity is the primary target or center of another entity’s competitive or adversarial rivalry.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:16 p.m.