Triple
T28073257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melbourne Derby |
E709464
|
entity |
| Predicate | formerNameOfClubInDerby |
P92907
|
FINISHED |
| Object | Melbourne Heart FC |
—
|
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: Melbourne Heart FC | Statement: [Melbourne Derby, formerNameOfClubInDerby, Melbourne Heart FC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerNameOfClubInDerby Context triple: [Melbourne Derby, formerNameOfClubInDerby, Melbourne Heart FC]
-
A.
nicknameOfClubFormerName
Indicates that a given nickname was used for a club when it had a former or previous official name.
-
B.
clubFormerName
chosen
Indicates that a sports club previously operated under a different official name.
-
C.
previousNameOfStadiumOfClub
Indicates that one entity is a former name previously used for the stadium belonging to a particular sports club.
-
D.
mostSuccessfulClubFormerName
Indicates that an entity was previously known by a different name during the period when it held the status of most successful club.
-
E.
predecessorClubNickname
Indicates that one club’s nickname was previously used by another club that served as its predecessor.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: April 27, 2026, 8:47 p.m.