Triple
T32202391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isla Queullín |
E822576
|
entity |
| Predicate | hasNearbyGeographicEntity |
P61362
|
FINISHED |
| Object | Chiloé Island |
—
|
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: Chiloé Island | Statement: [Isla Queullín, hasNearbyGeographicEntity, Chiloé Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyGeographicEntity Context triple: [Isla Queullín, hasNearbyGeographicEntity, Chiloé Island]
-
A.
hasNearbyGeographicalArea
Indicates that one geographical area is located in close spatial proximity to another geographical area.
-
B.
nearbyTo
chosen
Indicates that one entity is located close in distance or position to another entity.
-
C.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
-
D.
hasNearbyCityArea
Indicates that one area is geographically close to or adjacent to a city area.
-
E.
hasNearbyLandUse
Indicates that one land area is located close to another area characterized by a specific type of land use.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: May 1, 2026, 12:36 a.m.