Triple
T23840206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austria–Italy |
E590965
|
entity |
| Predicate | keyAgreementYear |
P117579
|
FINISHED |
| Object | 1946 |
—
|
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: 1946 | Statement: [Austria–Italy, keyAgreementYear, 1946]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyAgreementYear Context triple: [Austria–Italy, keyAgreementYear, 1946]
-
A.
keyAgreement
Indicates that two or more parties participate in a cryptographic process to establish a shared secret key for secure communication.
-
B.
agreementYear
chosen
Indicates the calendar year in which an agreement between the related entities was made, signed, or came into effect.
-
C.
keyUse
Indicates that one entity is used as a key or means of access, control, or identification for another entity.
-
D.
keyProposal
Indicates that a proposal plays a central or primary role within a broader plan, decision, or set of proposals.
-
E.
hasKeyAgreement
Indicates that two parties share or have established a cryptographic key agreement used to securely derive a common secret key.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c886aab081909ad896abe383afb9 |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:08 p.m.