Triple
T33406082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Special |
E855440
|
entity |
| Predicate | hasInteriorDetail |
P6655
|
FINISHED |
| Object | embossed California Special logos |
—
|
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: embossed California Special logos | Statement: [California Special, hasInteriorDetail, embossed California Special logos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteriorDetail Context triple: [California Special, hasInteriorDetail, embossed California Special logos]
-
A.
hasInteriorFeature
chosen
Indicates that an entity contains or includes a specific feature within its interior space.
-
B.
hasInteriorItem
Indicates that one entity contains another entity as an item located within its interior.
-
C.
hasRichInteriorDecoration
Indicates that an entity features elaborate, ornate, or luxuriously detailed interior decoration.
-
D.
hasInteriorColor
Indicates that an entity possesses a specific color used on its interior surfaces or internal parts.
-
E.
hasInteriorBehavior
Indicates that an entity exhibits a particular behavior or set of behaviors within its internal or enclosed space.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffe8ebe9fc8190b1934a3c4074370c |
completed | May 10, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69ffe83a5de88190bed3e8bac86e8760 |
completed | May 10, 2026, 2:06 a.m. |
Created at: May 1, 2026, 1:36 a.m.