Triple
T13604017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artur Axmann |
E325013
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Axmann |
E325013
|
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: Axmann | Statement: [Artur Axmann, familyName, Axmann]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Axmann Context triple: [Artur Axmann, familyName, Axmann]
-
A.
Axmann
chosen
Axmann is a German surname most notably borne by Artur Axmann, a leader of the Hitler Youth during the Nazi era.
-
B.
Ammann
Ammann is a surname most notably associated with Othmar Ammann, the Swiss-American civil engineer renowned for designing many of New York City's major suspension bridges.
-
C.
Kupferhammer
Kupferhammer is a locality within the town of Eberswalde in the state of Brandenburg, Germany.
-
D.
Garrel
Garrel is a rural municipality in Lower Saxony, Germany, known for its agriculture and location within the Cloppenburg district.
-
E.
Albertin
Albertin is a given name, typically a variant of Albertine, used as a personal name in some European languages.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb07ca07481909c45da551ea61ab4 |
completed | April 12, 2026, 2:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f77f93ec588190993baec788d22670 |
completed | May 3, 2026, 5:02 p.m. |
Created at: April 9, 2026, 9:50 p.m.