Triple
T23580346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dayton Way |
E582182
|
entity |
| Predicate | isTouristAttractionArea |
P530
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Dayton Way, isTouristAttractionArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTouristAttractionArea Context triple: [Dayton Way, isTouristAttractionArea, true]
-
A.
isPartOfTouristArea
Indicates that one entity is located within or belongs to a designated tourist area or tourist-focused region.
-
B.
containsTouristArea
Indicates that a place or region includes within its boundaries an area primarily designated or recognized for tourism activities.
-
C.
hasTouristAttractionRole
Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
-
D.
isTouristDestination
chosen
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
-
E.
isScenicArea
Indicates that a location is recognized as a scenic area, typically valued for its natural beauty or visually appealing surroundings.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b02c265c819094728220d77172c6 |
completed | April 29, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:39 p.m.