Triple
T399327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kollaa |
E9243
|
entity |
| Predicate | sloganMeaning |
P8493
|
FINISHED |
| Object | "Kollaa will hold" |
—
|
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: "Kollaa will hold" | Statement: [Battle of Kollaa, sloganMeaning, "Kollaa will hold"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sloganMeaning Context triple: [Battle of Kollaa, sloganMeaning, "Kollaa will hold"]
-
A.
sloganUsedIn
Indicates that a particular slogan is employed or featured within a specific context, such as a campaign, advertisement, or organization.
-
B.
meaningOfPhrase
chosen
Indicates that one entity expresses or defines the semantic content or interpretation of a given phrase.
-
C.
titleMeaning
Indicates that one entity expresses or explains the meaning, significance, or interpretation of another entity’s title.
-
D.
mottoType
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
E.
translationOfMotto
Indicates that one motto is a translation of another motto in a different language.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ec8d0ca881909d786e8eed9b6748 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96d17d08190878d3a68b17d51ca |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.