Triple
T14824729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castlemaine Perkins Brewery |
E348540
|
entity |
| Predicate | hasSignificantBrandColor |
P48662
|
FINISHED |
| Object | yellow |
—
|
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: yellow | Statement: [Castlemaine Perkins Brewery, hasSignificantBrandColor, yellow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignificantBrandColor Context triple: [Castlemaine Perkins Brewery, hasSignificantBrandColor, yellow]
-
A.
usesBrandColor
Indicates that one entity applies or displays another entity’s official brand color in its appearance, design, or materials.
-
B.
hasCapColor
Indicates that an entity possesses a cap whose color is specified by the related value.
-
C.
containsColor
Indicates that one entity includes or exhibits the color specified by another entity.
-
D.
hasBrandIdentityElement
chosen
Indicates that an entity includes or is associated with a specific component of its overall brand identity (such as a logo, color scheme, or tagline).
-
E.
corporateColor
Indicates the official color or color scheme that represents a corporation’s brand or identity.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe7a8dc8190bcb5ecfa1cbf1601 |
completed | April 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:51 a.m.