Triple
T3270653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Tamar |
E68638
|
entity |
| Predicate | valleyDesignation |
P47007
|
FINISHED |
| Object | Area of Outstanding Natural Beauty |
—
|
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: Area of Outstanding Natural Beauty | Statement: [River Tamar, valleyDesignation, Area of Outstanding Natural Beauty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valleyDesignation Context triple: [River Tamar, valleyDesignation, Area of Outstanding Natural Beauty]
-
A.
valleyType
Indicates the specific kind or classification of a valley that characterizes the relationship between the entities.
-
B.
valleyUsedFor
Indicates that a valley serves a particular function, purpose, or activity for something or someone.
-
C.
hasValley
Indicates that one entity contains, features, or is characterized by the presence of a valley associated with the other entity.
-
D.
locatedInRiverValley
Indicates that something is situated within the geographical area of a river valley.
-
E.
territorialDesignation
Indicates that an entity is assigned, defined, or recognized in terms of a specific geographic or territorial area.
- F. None of above. chosen
Provenance (4 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adaff349148190beae8c0994b7ad83 |
completed | March 8, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69ada41d7eac8190ada4bf5f793d5c49 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada525bb2c8190b773efe6d696b6ab |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:09 p.m.