Triple
T31412309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis Bread Company |
E801299
|
entity |
| Predicate | originatedBrand |
P49828
|
FINISHED |
| Object | Panera Bread |
—
|
NE NERFINISHED |
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: Panera Bread | Statement: [St. Louis Bread Company, originatedBrand, Panera Bread]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatedBrand Context triple: [St. Louis Bread Company, originatedBrand, Panera Bread]
-
A.
brandFounded
Indicates that a specific brand was established or created at a particular point in time or by a particular founder or entity.
-
B.
parentBrandCountry
Indicates that a brand’s parent company is based in or associated with a specific country.
-
C.
brandingOrigin
Indicates the source or entity from which a particular brand, branding style, or brand identity originates.
-
D.
brandSource
chosen
Indicates that one entity is the originating or providing brand associated with another entity (such as a product, service, or content).
-
E.
brandOriginContext
Indicates the contextual relationship between a brand and the place, culture, or circumstances from which it originates.
- 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00bc079314819096271bba60bee52d |
completed | May 10, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_6a00bba5bd408190ace5db0c4a90dc6f |
completed | May 10, 2026, 5:08 p.m. |
Created at: April 30, 2026, 8:39 p.m.