Triple
T706736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfred |
E14115
|
entity |
| Predicate | cognateInLanguage |
P2525
|
FINISHED |
| Object | Alfred (German) |
E14115
|
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: Alfred (German) | Statement: [Alfred, cognateInLanguage, Alfred (German)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alfred (German) Context triple: [Alfred, cognateInLanguage, Alfred (German)]
-
A.
Alfred
chosen
Alfred is a masculine given name of English origin, historically popular in Anglo-Saxon and later English-speaking cultures.
-
B.
Wilhelm
Wilhelm is a Germanic given name, equivalent to William, historically borne by numerous European nobles, rulers, and notable figures.
-
C.
Ruprecht
Ruprecht is a German given name, cognate with Robert, traditionally borne by various historical figures and saints in German-speaking regions.
-
D.
Hans
Hans is a masculine given name of Germanic origin commonly used in Germanic and Scandinavian countries.
-
E.
Ludwig
Ludwig is a masculine given name of Germanic origin, historically associated with nobility and rulers and used in various forms across many 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_69a493494ec48190ae6751683625a9ba |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4aa9a1dcc81908bdb7b960765fde5 |
completed | March 1, 2026, 9:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a5dcb1795c8190a178e14509b8b271 |
completed | March 2, 2026, 6:53 p.m. |
Created at: March 1, 2026, 7:36 p.m.