Triple
T17787028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freeport, Maine |
E444043
|
entity |
| Predicate | hasRetailDistrict |
P25135
|
FINISHED |
| Object | outlet shopping district |
—
|
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: outlet shopping district | Statement: [Freeport, Maine, hasRetailDistrict, outlet shopping district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRetailDistrict Context triple: [Freeport, Maine, hasRetailDistrict, outlet shopping district]
-
A.
hasRetailArea
chosen
Indicates that an entity possesses or includes a designated space used for retail or commercial sales activities.
-
B.
hasRetailPresenceIn
Indicates that an entity conducts retail operations or maintains a retail outlet, store, or sales presence within a specified location.
-
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.
hasShoppingDistrictType
Indicates that an entity is associated with a particular type or category of shopping district.
-
E.
hasShoppingDistrictName
Indicates that an entity’s shopping district is identified by a specific name.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487938418819096016ad717b014e6 |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.