Triple
T9480019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conrad |
E228611
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Konrad |
E60724
|
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: Konrad | Statement: [Conrad, hasVariant, Konrad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Konrad Context triple: [Conrad, hasVariant, Konrad]
-
A.
Konrad
chosen
Konrad is a masculine given name of German origin, historically borne by several notable figures including statesmen, nobles, and religious leaders.
-
B.
Conrad the Peaceful
Conrad the Peaceful was a 10th-century King of Burgundy who later became King of Italy and Holy Roman Emperor, noted for his relatively tranquil and conciliatory reign.
-
C.
Erwin
Erwin is a masculine given name of German origin, historically associated with figures such as the World War II field marshal Erwin Rommel.
-
D.
Othmar
Othmar is a masculine given name of Germanic origin, notably borne by the Swiss-American civil engineer Othmar Ammann.
-
E.
Reinhard
Reinhard is a masculine German given name historically borne by several notable figures, including high-ranking officials in Nazi Germany.
- 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_69ca84730a5081908de282651019bf2f |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd8016813881908dafc026779c89c4 |
completed | April 1, 2026, 8:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d12cf7526c8190b96693bdc13743d5 |
completed | April 4, 2026, 3:23 p.m. |
Created at: March 30, 2026, 7:54 p.m.