Triple
T9135017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Navy Outlet |
E219177
|
entity |
| Predicate | storeEnvironment |
P853
|
FINISHED |
| Object | self-service retail |
—
|
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: self-service retail | Statement: [Old Navy Outlet, storeEnvironment, self-service retail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storeEnvironment Context triple: [Old Navy Outlet, storeEnvironment, self-service retail]
-
A.
storesConfigurationFor
Indicates that one entity holds or maintains configuration settings that are used by or apply to another entity.
-
B.
store
Indicates that one entity keeps or holds another entity in a place or system for future use or access.
-
C.
supportsEnvironment
Indicates that one entity provides the necessary conditions, compatibility, or resources for another entity to operate or exist within a particular environment.
-
D.
environmentType
chosen
Indicates the kind or category of environment associated with an entity or situation.
-
E.
storageFacility
Indicates a relationship where one entity serves as a place or facility used to store another entity or its items.
- 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8de0dec8190978c80b9ec8bf25c |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.