Triple
T25547007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chester |
E640335
|
entity |
| Predicate | hasTouristDesignation |
P62013
|
FINISHED |
| Object | popular tourist destination |
—
|
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: popular tourist destination | Statement: [Chester, hasTouristDesignation, popular tourist destination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTouristDesignation Context triple: [Chester, hasTouristDesignation, popular tourist destination]
-
A.
touristDesignation
chosen
Indicates that a place or entity has been formally identified or labeled as a tourist attraction or destination.
-
B.
hasScenicDesignationSince
Indicates that an entity has held an official scenic designation continuously since a specified date.
-
C.
cityLandmarkDesignation
Indicates that a particular landmark has been officially designated or recognized as a landmark by a specific city.
-
D.
hasMemorialDesignation
Indicates that an entity has been formally assigned a specific memorial status, title, or designation in commemoration of something or someone.
-
E.
hasArchaeologicalParkStatus
Indicates that an entity has been officially designated and recognized as an archaeological park.
- 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 21, 2026, 3:34 p.m.