Triple
T25117108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playa de Melenara |
E629157
|
entity |
| Predicate | hasCoastalSculpture |
P160067
|
FINISHED |
| Object | bronze statue of a swimmer in the sea |
—
|
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: bronze statue of a swimmer in the sea | Statement: [Playa de Melenara, hasCoastalSculpture, bronze statue of a swimmer in the sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalSculpture Context triple: [Playa de Melenara, hasCoastalSculpture, bronze statue of a swimmer in the sea]
-
A.
hasCoastalLandmarks
chosen
Indicates that an entity possesses or is associated with notable geographic or cultural features located along a coast.
-
B.
hasCoastalSection
Indicates that a geographic entity includes at least one section of land that directly borders a sea or ocean.
-
C.
hasCoastalCharacteristic
Indicates that an entity possesses a feature, quality, or condition specifically related to coastal or shoreline environments.
-
D.
isCoastalLandmarkOf
Indicates that a landmark is located on or very near the coast of a specified geographic area or body of water.
-
E.
areCoastal
Indicates that the entities are located on or adjacent to a coastline or seashore.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 18, 2026, 6:27 a.m.