Triple
T14002217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siegfried Kohl |
E336854
|
entity |
| Predicate | hasSurnameLanguage |
P41819
|
FINISHED |
| Object | German |
—
|
LITERAL 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: German | Statement: [Siegfried Kohl, hasSurnameLanguage, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurnameLanguage Context triple: [Siegfried Kohl, hasSurnameLanguage, German]
-
A.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
-
B.
hasFamilyNameInLanguage
Indicates that an entity has a specific family name as expressed or written in a particular language.
-
C.
hasSeptSurname
Indicates that an entity bears a surname associated with a particular sept (a family subgroup or clan division).
-
D.
hasFullNameLanguage
chosen
Indicates that the language in which a full name is expressed is associated with that full name.
-
E.
hasComponentSurname
Indicates that an entity’s full name includes a specified surname as one of its component parts.
- F. None of above.
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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed06a50819093ddc64f55050689 |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:19 p.m.