Triple
T12595770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | zaque |
E300725
|
entity |
| Predicate | coRulerRegion |
P105597
|
FINISHED |
| Object | southern territories of the Muisca Confederation |
—
|
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: southern territories of the Muisca Confederation | Statement: [zaque, coRulerRegion, southern territories of the Muisca Confederation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coRulerRegion Context triple: [zaque, coRulerRegion, southern territories of the Muisca Confederation]
-
A.
coordinateRegion
Indicates that one region is geographically or spatially aligned with, or corresponds to, another region within a shared coordinate framework.
-
B.
rangeRegion
Indicates that one entity defines or corresponds to the spatial or conceptual region over which another entity extends or is applicable.
-
C.
coreRegionOf
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
-
D.
coRulerWith
Indicates that two or more entities share ruling authority over the same domain or polity at the same time.
-
E.
formationRegion
Indicates the place or area where something originates, is created, or comes into being.
- F. None of above. chosen
Provenance (4 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d954e351f88190869220d46e0ce282 |
completed | April 10, 2026, 7:52 p.m. |
Created at: April 9, 2026, 5:08 p.m.