Triple
T21725371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Acobamba |
E536260
|
entity |
| Predicate | hasTypeOfParties |
P89928
|
FINISHED |
| Object | colonial power and indigenous state |
—
|
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: colonial power and indigenous state | Statement: [Treaty of Acobamba, hasTypeOfParties, colonial power and indigenous state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfParties Context triple: [Treaty of Acobamba, hasTypeOfParties, colonial power and indigenous state]
-
A.
appliesToPartyType
chosen
Indicates that a rule, condition, or attribute is relevant to and affects a specific type or category of party (such as an individual, organization, or group).
-
B.
partiesAre
Indicates that certain entities are the participants or sides involved in a particular relationship, agreement, or event.
-
C.
arePartyTo
Indicates that the entities are participants or signatories in the same agreement, contract, or legal arrangement.
-
D.
hasPartiesDescription
Indicates that a relationship or event includes a textual description of the parties involved.
-
E.
hasMPParty
Indicates that a specified member of parliament is affiliated with a particular political party.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd972ed248190bd0d4ac43efccbfd |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:48 p.m.