Triple
T16909018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franco-Ottoman alliance |
E393018
|
entity |
| Predicate | grantedPrivilegeTo |
P55362
|
FINISHED |
| Object | French merchants in Ottoman ports |
—
|
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: French merchants in Ottoman ports | Statement: [Franco-Ottoman alliance, grantedPrivilegeTo, French merchants in Ottoman ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedPrivilegeTo Context triple: [Franco-Ottoman alliance, grantedPrivilegeTo, French merchants in Ottoman ports]
-
A.
grantedTo
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
-
B.
grantsPrivileges
chosen
Indicates that one entity confers specific rights, permissions, or advantages to another entity.
-
C.
grantedAs
Indicates that one entity is conferred, assigned, or bestowed in a particular role, status, or capacity to another entity.
-
D.
grantedBy
Indicates that a right, permission, or benefit is conferred or authorized by one entity to another.
-
E.
grantedIn
Indicates that something (such as a right, status, or permission) is formally conferred or authorized within a particular context, document, or jurisdiction.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3ca3bdc3081908a9b4f6e63405348 |
completed | April 18, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.