Triple
T37262094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Springs |
E924281
|
entity |
| Predicate | hasRetailFacility |
P87312
|
FINISHED |
| Object | general 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: general store | Statement: [Three Springs, hasRetailFacility, general store]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRetailFacility Context triple: [Three Springs, hasRetailFacility, general store]
-
A.
hasRetailPresenceIn
Indicates that an entity conducts retail operations or maintains a retail outlet, store, or sales presence within a specified location.
-
B.
hasRetailStores
chosen
Indicates that an entity operates or possesses one or more physical retail store locations.
-
C.
hasRetailNetwork
Indicates that an entity operates or is associated with a system of retail outlets or distribution channels through which products or services are sold.
-
D.
hasRetailFormat
Indicates that one entity operates or is organized according to a particular retail format or store type.
-
E.
hasRetailBoutiquesIn
Indicates that an entity operates or maintains retail boutiques located within a specified place or region.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.