Triple
T27031876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sotavento and Barlavento archipelago of Cape Verde |
E680938
|
entity |
| Predicate | divisionBy |
P889
|
FINISHED |
| Object | wind exposure |
—
|
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: wind exposure | Statement: [Sotavento and Barlavento archipelago of Cape Verde, divisionBy, wind exposure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionBy Context triple: [Sotavento and Barlavento archipelago of Cape Verde, divisionBy, wind exposure]
-
A.
divisionAssignment
Indicates that one entity is assigned to or associated with a particular division within an organizational or structural hierarchy.
-
B.
division
chosen
Indicates a relationship where one entity is separated or partitioned into parts, groups, or sections based on some criterion or operation.
-
C.
divisionResult
Indicates that one quantity is the result obtained by dividing one value by another.
-
D.
divisionResultOf
Indicates that one quantity is the numerical result obtained by dividing another quantity by a specified divisor.
-
E.
divisionAbove
Indicates that one entity is positioned in a higher or superior division, tier, or level relative to 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:14 a.m.