Triple
T25435821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armistice of Salasco |
E637369
|
entity |
| Predicate | signingAgent |
P45747
|
FINISHED |
| Object | Field Marshal Josef Radetzky von Radetz |
—
|
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: Field Marshal Josef Radetzky von Radetz | Statement: [Armistice of Salasco, signingAgent, Field Marshal Josef Radetzky von Radetz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signingAgent Context triple: [Armistice of Salasco, signingAgent, Field Marshal Josef Radetzky von Radetz]
-
A.
signatoryAuthority
Indicates that an entity has the legal power or authorization to sign documents or agreements on behalf of another party.
-
B.
signerOf
chosen
Indicates that an entity has signed or formally endorsed a document, agreement, or statement.
-
C.
agencySignedWith
Indicates that a formal agreement or contract has been established between an agency and another party.
-
D.
signGivenBy
Indicates that a sign (such as a signal, gesture, or indication) is produced or provided by one entity to another.
-
E.
signerParty
Indicates the party that formally signs or executes a document, agreement, or instrument.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 1:59 p.m.