Triple
T35346575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiwiana Town |
E1020756
|
entity |
| Predicate | marketingSloganRole |
P41673
|
FINISHED |
| Object | town branding for Ōtorohanga |
—
|
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: town branding for Ōtorohanga | Statement: [Kiwiana Town, marketingSloganRole, town branding for Ōtorohanga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketingSloganRole Context triple: [Kiwiana Town, marketingSloganRole, town branding for Ōtorohanga]
-
A.
sloganConcept
Indicates that a particular concept, idea, or theme is expressed or represented by a given slogan.
-
B.
promotionalRole
Indicates that an entity serves in a capacity focused on promoting, advertising, or publicizing another entity, product, or activity.
-
C.
brandingRole
chosen
Indicates the specific function or responsibility an entity has in creating, managing, or representing a brand within a branding context.
-
D.
marketingNameOf
Indicates that one entity is the marketing or brand name used to promote or refer to another entity.
-
E.
sloganGivenBy
Indicates that a particular slogan is provided, coined, or assigned by a specific entity.
- 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.