Triple
T2808927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jakob Ammann |
E54120
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Ammann |
E54120
|
NE 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: Ammann | Statement: [Jakob Ammann, familyName, Ammann]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ammann Context triple: [Jakob Ammann, familyName, Ammann]
-
A.
Huldrych
Huldrych is the given name of Huldrych Zwingli, the influential Swiss reformer and key figure in the early Protestant Reformation.
-
B.
Othmar
Othmar is a masculine given name of Germanic origin, notably borne by the Swiss-American civil engineer Othmar Ammann.
-
C.
Reinhold
Reinhold is the given first name of Reince Priebus, the American attorney and former White House Chief of Staff under President Donald Trump.
-
D.
Wüthrich
Wüthrich is a Swiss surname most notably associated with Nobel Prize–winning chemist Kurt Wüthrich.
-
E.
Jakob Ammann
chosen
Jakob Ammann was a Swiss Anabaptist leader whose strict teachings and reforms in the late 17th century led to the formation of the Amish movement.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde3165b48190a43be5e6ad23deca |
completed | March 7, 2026, 8:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afce97c3008190a966441d719d1d1c |
completed | March 10, 2026, 7:56 a.m. |
Created at: March 6, 2026, 9:59 p.m.