Triple
T24549207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praia do Amor |
E607311
|
entity |
| Predicate | shorelineShape |
P71569
|
FINISHED |
| Object | heart-shaped at low tide |
—
|
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: heart-shaped at low tide | Statement: [Praia do Amor, shorelineShape, heart-shaped at low tide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shorelineShape Context triple: [Praia do Amor, shorelineShape, heart-shaped at low tide]
-
A.
shorelineLength
Indicates the total measured extent of a land area’s boundary where it meets a body of water.
-
B.
formsShorelineOf
Indicates that one geographic feature constitutes or defines the boundary or edge (shoreline) of a body of water.
-
C.
shorelineIncludes
Indicates that a shoreline spatially contains or encompasses a specified coastal feature or segment.
-
D.
shorelineCharacteristic
chosen
Indicates the specific physical or environmental qualities that describe the nature or condition of a shoreline in relation to another entity.
-
E.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
- 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8cc2838819087d3fd429f12b525 |
completed | April 30, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:27 a.m.