Triple
T16830477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playa Mansa |
E409134
|
entity |
| Predicate | hasSeaConditionComparedToPlayaBrava |
P125010
|
FINISHED |
| Object | calmer |
—
|
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: calmer | Statement: [Playa Mansa, hasSeaConditionComparedToPlayaBrava, calmer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeaConditionComparedToPlayaBrava Context triple: [Playa Mansa, hasSeaConditionComparedToPlayaBrava, calmer]
-
A.
hasSeaCondition
Indicates that an entity is associated with or characterized by a particular state or condition of the sea.
-
B.
hasSurfBreak
Indicates a relationship where a location or area contains or is associated with a specific surf break suitable for surfing.
-
C.
hasBeachUse
Indicates that an entity is used for, designated for, or associated with beach-related activities or purposes.
-
D.
hasBeachNearby
Indicates that one location is situated close enough to another location to have convenient access to a beach.
-
E.
hasBeachTagRequirement
Indicates that something is subject to a specific requirement or condition related to beach access, use, or tagging.
- F. None of above. chosen
Provenance (4 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b316acc881909c686add53d72388 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:23 a.m.