Triple
T12395156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mascaypacha |
E296097
|
entity |
| Predicate | exclusivity |
P43059
|
FINISHED |
| Object | reserved for the Sapa Inca |
—
|
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: reserved for the Sapa Inca | Statement: [mascaypacha, exclusivity, reserved for the Sapa Inca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exclusivity Context triple: [mascaypacha, exclusivity, reserved for the Sapa Inca]
-
A.
exclusiveTo
chosen
Indicates that something is restricted or limited to a specific entity, group, or context and not shared with others.
-
B.
nonExclusive
Indicates that the relationship or access is shared among multiple parties and is not limited to a single, exclusive holder.
-
C.
exclusiveBenefit
Indicates that a benefit is provided to one party or group in a way that excludes others from receiving the same advantage.
-
D.
exclusivePower
Indicates that one entity holds sole authority or control over another entity or a specific domain, excluding others from sharing that power.
-
E.
exclusiveProducerOf
Indicates that one entity is the sole producer or manufacturer of another entity, with no other producers involved.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fd33f048190b205fd21dc513f6a |
completed | April 10, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.