Triple
T30035177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comarca of Fuerteventura (island-wide) |
E763135
|
entity |
| Predicate | hasMainIslandCity |
P316
|
FINISHED |
| Object | Puerto del Rosario |
—
|
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: Puerto del Rosario | Statement: [Comarca of Fuerteventura (island-wide), hasMainIslandCity, Puerto del Rosario]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainIslandCity Context triple: [Comarca of Fuerteventura (island-wide), hasMainIslandCity, Puerto del Rosario]
-
A.
isMainIsland
Indicates that an island is the primary or most significant island within a group, region, or country.
-
B.
hasMajorCity
chosen
Indicates that a location possesses at least one city of significant size, importance, or influence within its region or country.
-
C.
hasHeritageCityOnIsland
Indicates that a heritage city is located on, or geographically situated on, an island.
-
D.
hasMainHarbourOnIsland
Indicates that the primary harbour of a place or region is located on a specific island.
-
E.
hasInlandCity
Indicates that one entity has, contains, or is associated with a city located inland (away from the coast or major bodies of water).
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
Created at: April 29, 2026, 6:51 p.m.