Triple
T8088787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playa de la Cocina |
E188801
|
entity |
| Predicate | hasSeaOrientation |
P45094
|
FINISHED |
| Object | south of La Graciosa |
—
|
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: south of La Graciosa | Statement: [Playa de la Cocina, hasSeaOrientation, south of La Graciosa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeaOrientation Context triple: [Playa de la Cocina, hasSeaOrientation, south of La Graciosa]
-
A.
hasSeaCondition
Indicates that an entity is associated with or characterized by a particular state or condition of the sea.
-
B.
coastOrientation
chosen
Indicates the directional alignment or facing direction of a coastline relative to the cardinal or geographic axes.
-
C.
hasOcean
Indicates that a geographic region, country, or landmass is bordered by or directly adjacent to a particular ocean.
-
D.
hasSeaArmType
Indicates that an entity is associated with or characterized by a specific type of sea arm (such as a bay, gulf, fjord, or similar marine inlet).
-
E.
touchesSea
Indicates that one entity is in direct physical contact with the sea or coastline of another 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_69ca82b7b3e88190b9041ab0ef28b3cb |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb421c717c819089dd88c30a6401aa |
completed | March 31, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:29 p.m.