Triple
T20513150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qenqo archaeological site |
E503613
|
entity |
| Predicate | nearbySite |
P350
|
FINISHED |
| Object | Tambomachay |
—
|
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: Tambomachay | Statement: [Qenqo archaeological site, nearbySite, Tambomachay]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tambomachay Context triple: [Qenqo archaeological site, nearbySite, Tambomachay]
-
A.
Tambomachay
chosen
Tambomachay is an Inca archaeological site near Cusco, Peru, known for its finely crafted stonework and ceremonial water fountains.
-
B.
Tunupa
Tunupa is a prominent dormant volcano and sacred mountain in Bolivia, overlooking the Uyuni Salt Flat on the country’s Andean Altiplano.
-
C.
Chimbay
Chimbay is a town in the autonomous Republic of Karakalpakstan in northwestern Uzbekistan, serving as a local administrative and economic center in the region.
-
D.
Cumbe-Maita
Cumbe-Maita is a locality or settlement that forms part of the administrative area known as Capitol L-244.
-
E.
Tumebamba
Tumebamba was a prominent Inca imperial city in the northern highlands, serving as a key administrative and ceremonial center in what is now southern Ecuador.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dcd74c48190b050e25c20154c09 |
completed | April 20, 2026, 9:42 p.m. |
Created at: April 16, 2026, 11:36 a.m.