Triple
T38446963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huanca polities |
E906664
|
entity |
| Predicate | afterConquestRole |
P43767
|
FINISHED |
| Object | Inca provincial population |
—
|
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 provincial population | Statement: [Huanca polities, afterConquestRole, Inca provincial population]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterConquestRole Context triple: [Huanca polities, afterConquestRole, Inca provincial population]
-
A.
afterConquest
Indicates that one event, state, or condition occurs subsequent to and as a result of a conquest having taken place.
-
B.
afterConquestName
Indicates that an entity’s name is the one it is known by after a conquest or successful takeover has occurred.
-
C.
roleDuringConquest
Indicates the specific function, position, or capacity an entity held in relation to a particular conquest event.
-
D.
afterConquestBy
Indicates that one entity exists in a state, condition, or situation that occurs subsequent to and as a result of being conquered by another entity.
-
E.
roleAfterWar
chosen
Indicates the role or position an entity assumes following the end of a war or armed conflict.
- 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.