Triple
T37080257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Zimbabwe |
E918122
|
entity |
| Predicate | hasFanNicknameForFixture |
P74538
|
FINISHED |
| Object | Battle of Zim |
—
|
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: Battle of Zim | Statement: [Battle of Zimbabwe, hasFanNicknameForFixture, Battle of Zim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFanNicknameForFixture Context triple: [Battle of Zimbabwe, hasFanNicknameForFixture, Battle of Zim]
-
A.
hasNicknameForFixture
Indicates that one entity serves as a nickname or informal alternative name specifically for a given fixture.
-
B.
fanNicknameForFixture
chosen
Indicates that a particular nickname is used by fans to refer to a specific fixture or matchup.
-
C.
hasFanAbbreviation
Indicates that an entity is associated with an abbreviation or short form commonly used by fans to refer to it.
-
D.
hasHomeFansNickname
Indicates that an entity is known by a particular nickname specifically used by its home fans.
-
E.
fandomNickname
Indicates that one entity is the nickname used by fans to refer to another entity (such as a person, group, or work).
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: May 3, 2026, 4:14 p.m.