Triple
T5427330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destiny USA |
E121393
|
entity |
| Predicate | hasAnchorType |
P61394
|
FINISHED |
| Object | department stores |
—
|
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: department stores | Statement: [Destiny USA, hasAnchorType, department stores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnchorType Context triple: [Destiny USA, hasAnchorType, department stores]
-
A.
isAnchorOf
Indicates that one entity serves as a fixed reference or stabilizing point for another entity, to which the latter is attached or by which it is held in place.
-
B.
hasFormerAnchor
Indicates that an entity previously served as an anchor (e.g., host or main presenter) for another entity, but no longer holds that role.
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasAnchorStores
chosen
Indicates that a retail property or shopping center includes one or more major anchor stores as primary tenants.
-
E.
hasAlignmentType
Indicates that an entity possesses a specific alignment category or classification, such as moral, structural, or directional alignment.
- 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.