Triple
T16338622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Derby |
E396737
|
entity |
| Predicate | isDerbyBetween |
P45389
|
FINISHED |
| Object | two Perth-based AFL clubs |
—
|
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: two Perth-based AFL clubs | Statement: [Western Derby, isDerbyBetween, two Perth-based AFL clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDerbyBetween Context triple: [Western Derby, isDerbyBetween, two Perth-based AFL clubs]
-
A.
isDerby
Indicates that a competition or match is a derby, typically involving teams or participants from the same locality or with a strong rivalry.
-
B.
hasHomeDerbyFor
Indicates that one entity serves as the home venue or location where another entity’s derby event is held.
-
C.
playsInDerbyWith
chosen
Indicates that two entities participate together as opponents or competitors in the same derby event or match.
-
D.
playsInDerby
Indicates participation by an entity as a competitor or performer in a derby event.
-
E.
hasDerbyStatus
Indicates that an entity holds a specific status or classification related to a derby event or competition.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e6338081908aa03ee3dcbe5f70 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.