Triple
T30508917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bilbobus |
E776354
|
entity |
| Predicate | secondaryLanguageOfBrand |
P194011
|
FINISHED |
| Object | Spanish |
—
|
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: Spanish | Statement: [Bilbobus, secondaryLanguageOfBrand, Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryLanguageOfBrand Context triple: [Bilbobus, secondaryLanguageOfBrand, Spanish]
-
A.
secondaryLanguageSupport
chosen
Indicates that an entity provides assistance, services, or functionality in an additional (non-primary) language.
-
B.
primaryLanguageSide2
Indicates that the second entity in the relationship uses or is associated with the primary language specified.
-
C.
officialLanguageOfBranding
Indicates that a particular language is used as the official or primary language in the branding or marketing materials of an 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.
secondaryLanguageRegion
Indicates a region where a language is used in a secondary or supporting role rather than as the primary 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: April 29, 2026, 8:16 p.m.