Triple
T13173989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tumebamba |
E313051
|
entity |
| Predicate | ceremonialCenterOf |
P13725
|
FINISHED |
| Object | Inca Empire northern region |
—
|
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: Inca Empire northern region | Statement: [Tumebamba, ceremonialCenterOf, Inca Empire northern region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialCenterOf Context triple: [Tumebamba, ceremonialCenterOf, Inca Empire northern region]
-
A.
centralCeremonyLocation
chosen
Indicates the place that serves as the primary or focal site where a ceremony is held.
-
B.
tookPlaceAtReligiousCenter
Indicates that an event or action occurred at a religious center or place of worship.
-
C.
placeOfConsecration
Indicates the specific place where a religious or ceremonial consecration of something or someone took place.
-
D.
ecclesiasticalCenter
Indicates that a place functions as a primary religious or church administrative hub for a surrounding area or community.
-
E.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:14 p.m.