Triple
T29906618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio 2016 logo |
E759553
|
entity |
| Predicate | languageOfWordmark |
P5036
|
FINISHED |
| Object | Portuguese |
—
|
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: Portuguese | Statement: [Rio 2016 logo, languageOfWordmark, Portuguese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfWordmark Context triple: [Rio 2016 logo, languageOfWordmark, Portuguese]
-
A.
officialLanguageOfBranding
Indicates that a particular language is used as the official or primary language in the branding or marketing materials of an entity.
-
B.
emblemLanguage
chosen
Indicates that an emblem (such as a symbol or logo) is associated with or presented in a particular language.
-
C.
labelMarketingLanguage
Indicates that one entity is designated as the marketing-oriented label or phrasing used to promote or describe another entity.
-
D.
brandLanguageVariant
Indicates that one language variant of a brand is related to or derived from another language version of the same brand.
-
E.
serviceBrandLanguage
Indicates the language or languages in which a service brand communicates or is presented.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: April 29, 2026, 6:08 p.m.