Triple
T25039216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cantabrian coast |
E627061
|
entity |
| Predicate | hasMaritimeConditions |
P13023
|
FINISHED |
| Object | high rainfall |
—
|
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 rainfall | Statement: [Cantabrian coast, hasMaritimeConditions, high rainfall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritimeConditions Context triple: [Cantabrian coast, hasMaritimeConditions, high rainfall]
-
A.
hasSeaCondition
chosen
Indicates that an entity is associated with or characterized by a particular state or condition of the sea.
-
B.
hasMaritimeFeature
Indicates that one entity possesses, contains, or is characterized by a maritime-related feature such as a sea, coast, harbor, or other oceanic element.
-
C.
seaConditionAdaptation
Indicates how well an entity adjusts or responds to varying or challenging sea or ocean conditions.
-
D.
maritimeHazard
Indicates a condition, object, or situation at sea that poses a risk to vessels, navigation, or maritime operations.
-
E.
isMaritimeRoute
Indicates that one location is connected to another by a navigable sea or ocean route used for maritime transport.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 18, 2026, 6:08 a.m.