Triple
T37085658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Münsingen |
E918278
|
entity |
| Predicate | hasPlaceOfSignature |
P18545
|
FINISHED |
| Object | Münsingen |
—
|
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: Münsingen | Statement: [Treaty of Münsingen, hasPlaceOfSignature, Münsingen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlaceOfSignature Context triple: [Treaty of Münsingen, hasPlaceOfSignature, Münsingen]
-
A.
signatureLocation
chosen
Indicates the place or position where a signature is written, recorded, or otherwise applied.
-
B.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
C.
wasSignedAs
Indicates that an entity formally entered into or agreed to a contract, document, or role under a specified name, status, or terms.
-
D.
agreementSignedBy
Indicates that a particular agreement has been formally signed or executed by a specified party.
-
E.
noteSignature
Indicates that one entity serves as a signature or identifying mark attached to a note created or associated with another entity.
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: May 3, 2026, 4:14 p.m.