Triple
T33424872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quito–Galápagos |
E855945
|
entity |
| Predicate | destinationDesignation |
P49802
|
FINISHED |
| Object | UNESCO World Heritage Site |
—
|
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: UNESCO World Heritage Site | Statement: [Quito–Galápagos, destinationDesignation, UNESCO World Heritage Site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destinationDesignation Context triple: [Quito–Galápagos, destinationDesignation, UNESCO World Heritage Site]
-
A.
destinationFeature
Indicates the feature, place, or element that serves as the endpoint or target location of a movement, transfer, or directed relation.
-
B.
journeyDestination
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
C.
destinationCity
Indicates the city to which an entity is traveling, being sent, or ultimately directed.
-
D.
destinationOfVoyageTo
Indicates the endpoint location that a particular voyage or journey is directed toward or arrives at.
-
E.
designationFor
chosen
Indicates that one entity serves as the official title, label, or role name assigned 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e47f37848190aadb137c81760f1f |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.