Triple
T32359484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wari provincial administration |
E826819
|
entity |
| Predicate | hadProvincialExample |
P174185
|
FINISHED |
| Object | Pikillaqta |
—
|
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: Pikillaqta | Statement: [Wari provincial administration, hadProvincialExample, Pikillaqta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadProvincialExample Context triple: [Wari provincial administration, hadProvincialExample, Pikillaqta]
-
A.
hadProvince
Indicates that a governing entity possessed administrative control or jurisdiction over a specific province.
-
B.
isProvincial
Indicates that something belongs to, is characteristic of, or is administered at the level of a province rather than a national or local level.
-
C.
previousProvince
Indicates that one province was the immediately preceding administrative region of another in a temporal or historical sequence.
-
D.
laterProvince
Indicates that one administrative region or province succeeds another in time, coming into existence or effect after the other.
-
E.
affectedProvince
Indicates that a particular province is impacted or influenced by a specified event, action, or condition.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be93bb548190880e9671c1dd0f29 |
completed | May 3, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: May 1, 2026, 12:49 a.m.