Triple
T11595998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carpenter |
E275002
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Zimmermann |
E98929
|
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: Zimmermann | Statement: [Carpenter, hasVariant, Zimmermann]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zimmermann Context triple: [Carpenter, hasVariant, Zimmermann]
-
A.
Zimmermann
chosen
Zimmermann is a German surname commonly associated with the occupation of a carpenter or builder.
-
B.
von Hindenburg
Von Hindenburg is a German noble family name most famously associated with Paul von Hindenburg, the World War I field marshal and later President of Germany.
-
C.
Helmuth
Helmuth is a masculine given name of German origin, historically borne by several notable military and political figures.
-
D.
Arthur Zimmermann
Arthur Zimmermann was the German Foreign Secretary during World War I, best known for the Zimmermann Telegram that sought to draw Mexico into the war against the United States.
-
E.
Heideck
Heideck was a notable Philhellene, remembered for his support of the Greek cause during the Greek War of Independence.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8946790d08190924d60bb4b523250 |
completed | April 10, 2026, 6:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e8a7b72c888190b069d0ebaebd31d9 |
completed | April 22, 2026, 10:49 a.m. |
Created at: April 8, 2026, 9:38 p.m.