Triple
T5407299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Zsitvatorok |
E120922
|
entity |
| Predicate | effectOnTribute |
P53074
|
FINISHED |
| Object | reduced Habsburg financial obligations to Ottomans |
—
|
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: reduced Habsburg financial obligations to Ottomans | Statement: [Treaty of Zsitvatorok, effectOnTribute, reduced Habsburg financial obligations to Ottomans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnTribute Context triple: [Treaty of Zsitvatorok, effectOnTribute, reduced Habsburg financial obligations to Ottomans]
-
A.
effectOnMembers
Indicates the impact or influence that something has on the members of a group or organization.
-
B.
notableEffect
Indicates that one entity has a significant impact, consequence, or influence on another entity or situation.
-
C.
sacrificedTo
Indicates that one entity is offered or given up as a sacrifice in honor of, or to appease, another entity.
-
D.
reasonForTribute
Indicates the underlying cause, justification, or circumstance that explains why a tribute is given.
-
E.
eventEffect
chosen
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8793ab3c81909992b257d462a554 |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.