Triple
T29609458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Besaya |
E754672
|
entity |
| Predicate | valleyTraversedBy |
P119958
|
FINISHED |
| Object | Autovía A-67 |
—
|
NE NERFINISHED |
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: Autovía A-67 | Statement: [Besaya, valleyTraversedBy, Autovía A-67]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valleyTraversedBy Context triple: [Besaya, valleyTraversedBy, Autovía A-67]
-
A.
traversesValley
Indicates that an entity moves through or across a valley, passing from one side or area to another.
-
B.
valleyUsedBy
chosen
Indicates that a valley is utilized or traversed by a particular entity, such as for passage, habitation, or other activities.
-
C.
valleySystem
Indicates a relationship where a valley is part of, associated with, or characterized by a particular valley system or network of valleys.
-
D.
valleyType
Indicates the specific kind or classification of a valley that characterizes the relationship between the entities.
-
E.
valleyLocation
Indicates that one entity is located in, at, or within the geographic bounds of a valley relative to another entity or context.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66dea375881909684db997861425c |
completed | May 2, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:27 p.m.