Triple
T37080251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Zimbabwe |
E918122
|
entity |
| Predicate | hasLanguageOfSupporterChants |
P41747
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Battle of Zimbabwe, hasLanguageOfSupporterChants, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfSupporterChants Context triple: [Battle of Zimbabwe, hasLanguageOfSupporterChants, English]
-
A.
hasSignificantSupporterLanguage
Indicates that an entity is associated with language expressing notable endorsement, advocacy, or backing from supporters.
-
B.
hasFanChantPotential
Indicates that something (such as a song, phrase, or performance element) is well-suited to be adopted and enthusiastically chanted by a crowd or fanbase.
-
C.
hasChorusLanguage
Indicates that the language used in the chorus section of a work (such as a song or musical piece) is a specified language.
-
D.
languageOfChant
chosen
Indicates the language in which a chant is performed or expressed.
-
E.
hasLanguageOfProtest
Indicates that an entity expresses or embodies a language, style, or discourse of protest in relation to another entity or context.
- 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_69ffc704e1e88190884928a6a5c55a87 |
completed | May 9, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69ffc6b483d881908ad872e25fa6abc5 |
completed | May 9, 2026, 11:43 p.m. |
Created at: May 3, 2026, 4:14 p.m.