Triple
T11226766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cvetković–Maček Agreement |
E265714
|
entity |
| Predicate | deFactoTermination |
P11097
|
FINISHED |
| Object | 1941 |
—
|
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: 1941 | Statement: [Cvetković–Maček Agreement, deFactoTermination, 1941]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deFactoTermination Context triple: [Cvetković–Maček Agreement, deFactoTermination, 1941]
-
A.
natureOfTermination
Indicates the manner, cause, or conditions under which a relationship, contract, or employment is brought to an end.
-
B.
recommendedTerminationOf
Indicates that one party has advised or proposed that another party’s role, contract, or activity should be ended.
-
C.
deFactoEndDate
chosen
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
D.
deFactoSuspendedAfter
Indicates that one state, condition, or status effectively became suspended or inactive following another specified event or point in time.
-
E.
terminationMechanism
Indicates the process or method by which an ongoing state, activity, or relationship is brought to an end.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8ff7b40819089c835be710bc575 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.