Triple
T27652889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merrimack Premium Outlets |
E696908
|
entity |
| Predicate | attractsShoppersFrom |
P163515
|
FINISHED |
| Object | northern New England |
—
|
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: northern New England | Statement: [Merrimack Premium Outlets, attractsShoppersFrom, northern New England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attractsShoppersFrom Context triple: [Merrimack Premium Outlets, attractsShoppersFrom, northern New England]
-
A.
attractsShoppersFrom
chosen
Indicates a source location or entity draws shoppers away from or brings them in from another location or area.
-
B.
attractedMerchantsFrom
Indicates that one entity drew or lured merchants away from another entity or location.
-
C.
attractsDriversFrom
Indicates that one entity draws or pulls drivers away from another entity, causing them to choose or move to it instead.
-
D.
attractsCompetitorsFrom
Indicates that one entity draws or lures competitors away from another entity or location.
-
E.
attracts
Indicates that one entity exerts a force or influence that draws another entity toward it.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 2:33 p.m.