Triple
T7944819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australia Cup |
E184472
|
entity |
| Predicate | hasDrawMethod |
P9095
|
FINISHED |
| Object | random draw for each round |
—
|
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: random draw for each round | Statement: [Australia Cup, hasDrawMethod, random draw for each round]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDrawMethod Context triple: [Australia Cup, hasDrawMethod, random draw for each round]
-
A.
usesPointsForDraw
Indicates that an entity relies on or applies a points-based system to determine or execute a draw (such as a lottery, selection, or outcome).
-
B.
hasPlayingMethod
Indicates that there is a specific way, technique, or method by which something is played or performed.
-
C.
canRender
Indicates that one entity has the capability or functionality to generate or display another entity in a visual or presentable form.
-
D.
canBeDepictedAs
Indicates that one entity is capable of being visually represented or illustrated in the form or style of another entity.
-
E.
hasWorkingMethod
chosen
Indicates that one entity possesses or employs a functional method, procedure, or technique to achieve a particular task or outcome.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b285d3881909b2ac0b395538a8a |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.