Triple
T10783406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galápagos hotspot |
E254387
|
entity |
| Predicate | olderIslandsLocated |
P95458
|
FINISHED |
| Object | eastern Galápagos Islands |
—
|
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: eastern Galápagos Islands | Statement: [Galápagos hotspot, olderIslandsLocated, eastern Galápagos Islands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: olderIslandsLocated Context triple: [Galápagos hotspot, olderIslandsLocated, eastern Galápagos Islands]
-
A.
locatedInArchipelago
Indicates that one place or geographic entity is situated within or is part of a specific archipelago.
-
B.
nearestPopulatedIsland
Indicates that one island is the closest populated island to another specified location or island.
-
C.
islandOf
Indicates that one place is an island belonging to, located within, or geographically associated with another specified area or body of land/water.
-
D.
formerIslandOf
Indicates that one entity was previously an island associated with another entity, but no longer holds that status.
-
E.
associatedIsland
Indicates that one entity is related to or connected with a particular island in some relevant way.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d1b4bc8190871dd21265065705 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa334b8c819082eaf8537084c323 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:17 p.m.