Triple
T16346273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of 1518 with the Portuguese |
E396939
|
entity |
| Predicate | grantsPrivilegeType |
P66994
|
FINISHED |
| Object | commercial privileges |
—
|
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: commercial privileges | Statement: [Treaty of 1518 with the Portuguese, grantsPrivilegeType, commercial privileges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantsPrivilegeType Context triple: [Treaty of 1518 with the Portuguese, grantsPrivilegeType, commercial privileges]
-
A.
grantsPrivileges
Indicates that one entity confers specific rights, permissions, or advantages to another entity.
-
B.
grantedRightsType
chosen
Indicates the specific category or nature of rights that have been granted in a given permission or authorization relationship.
-
C.
grantsAbility
Indicates that one entity endows another entity with a specific capability or power that it did not previously possess.
-
D.
typeOfGrant
Indicates the specific category or kind of grant associated with an entity.
-
E.
granteeType
Indicates the classification or category of the entity that receives a grant or is granted a right, benefit, or permission.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da0ec7e08190982a0de8ba5da105 |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.