Triple
T35586826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RiverTown Crossings |
E1028379
|
entity |
| Predicate | isRegionalDestinationFor |
P110841
|
FINISHED |
| Object | shopping |
—
|
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: shopping | Statement: [RiverTown Crossings, isRegionalDestinationFor, shopping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegionalDestinationFor Context triple: [RiverTown Crossings, isRegionalDestinationFor, shopping]
-
A.
isRegionalDestination
chosen
Indicates that a place serves as a primary travel or attraction target within a specific geographic region.
-
B.
hasDestinationRegion
Indicates that something is directed, sent, or intended to arrive at a particular geographic or logical region as its destination.
-
C.
isRegionalPort
Indicates that a port serves primarily a specific region or local area rather than functioning as a major national or international hub.
-
D.
isRegional
Indicates that something pertains to, is characteristic of, or is limited to a specific geographic region or area.
-
E.
isFromRegion
Indicates that one entity originates from, is associated with, or belongs to a specified geographic 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_69f76e0495a081909beced418558c0b4 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:04 p.m.