Triple
T20608540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loir River valley |
E506379
|
entity |
| Predicate | tourismCharacter |
P84159
|
FINISHED |
| Object | quiet |
—
|
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: quiet | Statement: [Loir River valley, tourismCharacter, quiet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourismCharacter Context triple: [Loir River valley, tourismCharacter, quiet]
-
A.
touristCharacter
Indicates that an entity has the role, behavior, or qualities characteristic of a tourist in relation to another entity or context.
-
B.
tourismCharacteristic
chosen
Indicates that something has a specific feature, quality, or attribute relevant to tourism, such as what makes a place, service, or activity notable or suitable for tourists.
-
C.
tourismFeature
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
D.
travelCharacteristic
Indicates a quality, feature, or attribute that characterizes how travel or movement is conducted or experienced.
-
E.
subjectOfTour
Indicates that an entity serves as the main focus, destination, or theme of a tour.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aad4b0bc819097b785f921561f36 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.