Triple
T996752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cusco |
E21511
|
entity |
| Predicate | localName |
P657
|
FINISHED |
| Object | Qosqo |
E21511
|
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: Qosqo | Statement: [Cusco, localName, Qosqo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Qosqo Context triple: [Cusco, localName, Qosqo]
-
A.
Cusco
chosen
Cusco is a historic city in southeastern Peru that served as the capital of the Inca Empire and is now a major gateway to Machu Picchu.
-
B.
Qhapaq Ñan
Qhapaq Ñan is the vast Andean road system built by the Inca civilization, spanning thousands of kilometers to connect major centers across their mountainous empire.
-
C.
Chavín de Huántar
Chavín de Huántar is an ancient ceremonial and archaeological site in the Peruvian Andes that served as the religious and cultural center of the Chavín civilization.
-
D.
Huaca Pucllana
Huaca Pucllana is a pre-Inca adobe pyramid and ceremonial complex located in the Miraflores district of Lima, Peru.
-
E.
Sacsayhuamán
Sacsayhuamán is a monumental Inca fortress and ceremonial complex overlooking Cusco, renowned for its massive precisely fitted stone walls and archaeological significance.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4df6dcc819084a7c0a50637a2c2 |
completed | March 1, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac3ba52ebc819084e3d003a3ec8417 |
completed | March 7, 2026, 2:52 p.m. |
Created at: March 1, 2026, 7:41 p.m.