Triple
T2907631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Túpac Amaru |
E63603
|
entity |
| Predicate | residence |
P75
|
FINISHED |
| Object | Vilcabamba |
E147954
|
NE 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: Vilcabamba | Statement: [Túpac Amaru, residence, Vilcabamba]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vilcabamba Context triple: [Túpac Amaru, residence, Vilcabamba]
-
A.
Vilcabamba
chosen
Vilcabamba was the remote Andean stronghold that served as the last refuge of the Inca resistance against Spanish conquest.
-
B.
Collasuyu
Collasuyu was the southeastern quarter of the Inca Empire, encompassing the highland and lowland regions around Lake Titicaca and extending into parts of present-day Bolivia, Chile, and Argentina.
-
C.
Chinchaysuyu
Chinchaysuyu was the northwestern quarter of the Inca Empire, encompassing coastal and highland regions that are now parts of Peru, Ecuador, and Colombia.
-
D.
Cuntisuyu
Cuntisuyu was one of the four main administrative and territorial divisions of the Inca Empire, located to the southwest of Cusco.
-
E.
Urubamba
Urubamba is a town in Peru’s Sacred Valley of the Incas, known as a gateway to Machu Picchu and surrounding Andean archaeological sites.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0d1dcf881909b3ae58d7cdfd9cd |
completed | March 7, 2026, 8:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1de8b9378819084861d65dd2b9528 |
completed | March 11, 2026, 9:28 p.m. |
Created at: March 6, 2026, 10:11 p.m.