Triple
T29496754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia do Orzán |
E748249
|
entity |
| Predicate | formsContinuousStretchWith |
P162796
|
FINISHED |
| Object | Praia de Riazor |
—
|
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: Praia de Riazor | Statement: [Praia do Orzán, formsContinuousStretchWith, Praia de Riazor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsContinuousStretchWith Context triple: [Praia do Orzán, formsContinuousStretchWith, Praia de Riazor]
-
A.
extendsContinuouslyTo
chosen
Indicates that one entity stretches or reaches from its starting point to another entity without interruption or breaks along the way.
-
B.
continuityFrom
Indicates that one entity continues, extends, or proceeds directly from another in a seamless or unbroken manner.
-
C.
isStretchOf
Indicates that one linear feature (such as a road, river, or path) constitutes a continuous segment or portion of another, longer linear feature.
-
D.
stretchedFrom
Indicates that one entity extends or reaches out in space or time starting at another specified entity or point.
-
E.
continuityType
Indicates the specific manner or pattern in which continuity is maintained or transitions occur between related elements or states.
- 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_69f0bd448c6881908aa6b475cefd5ddc |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 28, 2026, 4:19 p.m.