Triple
T26087411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venetian conquest of the Morea |
E658020
|
entity |
| Predicate | treatyConcludedBy |
P162911
|
FINISHED |
| Object | Treaty of Karlowitz |
—
|
NE NERFINISHED |
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: Treaty of Karlowitz | Statement: [Venetian conquest of the Morea, treatyConcludedBy, Treaty of Karlowitz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatyConcludedBy Context triple: [Venetian conquest of the Morea, treatyConcludedBy, Treaty of Karlowitz]
-
A.
treatyConcluded
Indicates that a formal agreement or treaty has been officially finalized and brought into force between the involved parties.
-
B.
treatyOf
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
-
C.
treatySignedWith
Indicates that a formal treaty or agreement has been officially signed between two parties.
-
D.
treatySignedFor
Indicates that a formal treaty has been signed on behalf of, or in representation of, a particular entity, cause, or subject.
-
E.
resultOfTreaties
Indicates that something exists, occurs, or holds true as a consequence or outcome of one or more treaties.
- F. None of above. chosen
Provenance (4 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f62e83045c8190a424a2e401a88e9e |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d886828819080ec2f742b9449e3 |
completed | May 2, 2026, 4:59 p.m. |
Created at: April 26, 2026, 7:44 p.m.