Triple
T15116379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Original Rivalry (with Melbourne Victory FC) |
E361049
|
entity |
| Predicate | isDerbyType |
P81009
|
FINISHED |
| Object | interstate rivalry |
—
|
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: interstate rivalry | Statement: [Original Rivalry (with Melbourne Victory FC), isDerbyType, interstate rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDerbyType Context triple: [Original Rivalry (with Melbourne Victory FC), isDerbyType, interstate rivalry]
-
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.
typeOfDerby
chosen
Indicates that one entity is a specific kind or category of derby in relation to another entity.
-
C.
hasDerbyStatus
Indicates that an entity holds a specific status or classification related to a derby event or competition.
-
D.
derby
Indicates a competitive match or contest, typically between closely linked or rival entities (such as teams from the same area or group).
-
E.
derbyInLeagueSystem
Indicates that a derby (a match between local rivals) takes place within, and is organized as part of, a specific league system.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0059ca9048190b742e70e818ee64f |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:05 a.m.