Triple
T21486533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australia vs England, 1987 Cricket World Cup Final |
E530129
|
entity |
| Predicate | AustraliaOversFaced |
P144551
|
FINISHED |
| Object | 50 |
—
|
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: 50 | Statement: [Australia vs England, 1987 Cricket World Cup Final, AustraliaOversFaced, 50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AustraliaOversFaced Context triple: [Australia vs England, 1987 Cricket World Cup Final, AustraliaOversFaced, 50]
-
A.
AustraliaOvers
Indicates a relationship where one entity surpasses, exceeds, or goes beyond another in the specific context associated with Australia.
-
B.
australiaSupports
Indicates that Australia provides assistance, endorsement, or backing to another entity or action.
-
C.
australiaMemberOf
Indicates that an entity (such as an organization, group, or agreement) includes Australia as a member.
-
D.
USRecognizedAustralia
Indicates that the United States formally acknowledged Australia as a sovereign state or legitimate government.
-
E.
isInAustralia
Indicates that the subject is located within the geographical boundaries of Australia.
- F. None of above. chosen
Provenance (4 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea370adc8190b79fe26e2eba1dca |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:22 p.m.