Triple
T24657380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anse Severe |
E610429
|
entity |
| Predicate | bestTimeForSnorkeling |
P156923
|
FINISHED |
| Object | high 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: high tide | Statement: [Anse Severe, bestTimeForSnorkeling, high tide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestTimeForSnorkeling Context triple: [Anse Severe, bestTimeForSnorkeling, high tide]
-
A.
bestDiveConditions
Indicates that the environmental and situational factors for diving are at their most favorable or optimal level.
-
B.
hasBestTimeForSurfing
Indicates that a particular time or period is considered optimal for surfing conditions at a given location.
-
C.
snorkelingRequirement
Indicates that a certain condition, skill, equipment, or rule is required in order for an entity to engage in snorkeling.
-
D.
hasDivingSeason
Indicates that there is a specific time period during which diving activities are permitted, optimal, or typically occur for a given entity or location.
-
E.
bestTimeToVisitForWildlife
Indicates the most favorable time period to visit a place specifically for observing wildlife activity or diversity.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f41010f06c81908ee7f773220df14f |
completed | May 1, 2026, 2:29 a.m. |
Created at: April 18, 2026, 2:34 a.m.