Triple
T37984923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bloods |
E947660
|
entity |
| Predicate | associatedWithNicknameOf |
P204512
|
FINISHED |
| Object | South Melbourne Football Club |
E280990
|
NE 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: South Melbourne Football Club | Statement: [The Bloods, associatedWithNicknameOf, South Melbourne Football Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithNicknameOf Context triple: [The Bloods, associatedWithNicknameOf, South Melbourne Football Club]
-
A.
associatedWithArtistNickname
Indicates that an entity is connected to or identified by a particular artist’s nickname or pseudonym.
-
B.
usesNicknameOf
Indicates that one entity refers to another entity by a nickname derived from or associated with that other entity’s name.
-
C.
usesNicknameIn
Indicates that one entity refers to another entity by a specific nickname within a particular context or setting.
-
D.
pairedNickname
Indicates that two entities share or are associated with a complementary or matching set of nicknames.
-
E.
usesNicknameFor
Indicates that one entity habitually refers to another entity by a nickname rather than their formal or given name.
- F. None of above. chosen
Provenance (5 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a417b19c1748190bbb47d269dec2fab |
completed | June 28, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:20 p.m.