Triple
T28663240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaufmann’s |
E725521
|
entity |
| Predicate | flagshipStoreType |
P126465
|
FINISHED |
| Object | multi-story department store |
—
|
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: multi-story department store | Statement: [Kaufmann’s, flagshipStoreType, multi-story department store]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagshipStoreType Context triple: [Kaufmann’s, flagshipStoreType, multi-story department store]
-
A.
flagshipStoreLocation
Indicates the location where an organization’s primary or most prominent store is situated.
-
B.
flagshipStoreBuildingUse
chosen
Indicates that a building is used as the primary or flagship retail store location for a brand or company.
-
C.
flagshipType
Indicates that one entity is the primary or most important representative (flagship) of a particular type, category, or group defined by the other entity.
-
D.
flagshipStoreBuildingStyle
Indicates the architectural style or design type characteristic of a brand’s flagship store building.
-
E.
isFlagshipServiceOf
Indicates that a particular service is the primary, leading, or most prominent offering of a given organization or provider.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 4:59 a.m.