Triple
T24747021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cala Sant Vicenç |
E619026
|
entity |
| Predicate | hasCove |
P118123
|
FINISHED |
| Object | Cala Barques |
—
|
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: Cala Barques | Statement: [Cala Sant Vicenç, hasCove, Cala Barques]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCove Context triple: [Cala Sant Vicenç, hasCove, Cala Barques]
-
A.
isCove
Indicates that one location or geographic feature is a small, sheltered bay or inlet along a coastline or shore.
-
B.
hasCP
Indicates that an entity possesses, is associated with, or is characterized by a specific CP (such as a control point, contact person, or configuration parameter), depending on the domain context.
-
C.
hasCoverFeature
Indicates that one entity serves as a prominent or featured element on the cover of another entity (such as a publication, product, or media item).
-
D.
hasNearbyCove
chosen
Indicates that one location is situated close to a small sheltered bay or cove.
-
E.
hasNave
Indicates that one entity (typically a building or structure) possesses or includes a nave as a distinct architectural part.
- 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 4:22 a.m.