Triple
T30025215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avenida Lúcio Costa |
E762861
|
entity |
| Predicate | hasDirectionRelativeToCoast |
P156117
|
FINISHED |
| Object | parallel to shoreline |
—
|
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: parallel to shoreline | Statement: [Avenida Lúcio Costa, hasDirectionRelativeToCoast, parallel to shoreline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionRelativeToCoast Context triple: [Avenida Lúcio Costa, hasDirectionRelativeToCoast, parallel to shoreline]
-
A.
positionRelativeToCoast
Indicates the spatial relationship of something to a coastline, such as its distance or orientation relative to the coast.
-
B.
coastOrientation
Indicates the directional alignment or facing direction of a coastline relative to the cardinal or geographic axes.
-
C.
hasNearbyCoast
Indicates that one location is situated close to a coastline or seashore.
-
D.
seaOrientation
chosen
Indicates the directional relationship of something relative to the sea or coastline (e.g., which way it faces or is aligned).
-
E.
navigatedAlongCoastOf
Indicates that an entity traveled or steered a course following the coastline of another geographic entity.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: April 29, 2026, 6:48 p.m.