Triple
T32359417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andean Middle Horizon |
E826818
|
entity |
| Predicate | hasDominantPolity |
P1815
|
FINISHED |
| Object | Wari culture |
—
|
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: Wari culture | Statement: [Andean Middle Horizon, hasDominantPolity, Wari culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDominantPolity Context triple: [Andean Middle Horizon, hasDominantPolity, Wari culture]
-
A.
hasPolity
chosen
Indicates that one entity possesses, controls, or is associated with a particular political organization, governance structure, or state-like authority.
-
B.
hasDominion
Indicates that one entity holds authority, control, or governing power over another entity or domain.
-
C.
hasSovereignPowerOver
Indicates that one entity holds ultimate governing authority or supreme ruling power over another entity.
-
D.
hasDeFactoSovereign
Indicates that one entity effectively exercises sovereign authority or control over another entity in practice, regardless of formal or legal recognition.
-
E.
hasDomesticDominanceIn
Indicates that an entity holds a leading or dominant position within a specified domestic (home-country) market or context.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 12:49 a.m.