Triple
T7941083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krueger |
E184390
|
entity |
| Predicate | fieldOfEtymology |
P35085
|
FINISHED |
| Object | German onomastics |
—
|
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 onomastics | Statement: [Krueger, fieldOfEtymology, German onomastics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldOfEtymology Context triple: [Krueger, fieldOfEtymology, German onomastics]
-
A.
etymologicalField
chosen
Indicates that one term belongs to a particular semantic or conceptual domain relevant to its etymological origin or historical development.
-
B.
etymologicalLanguage
Indicates the language from which a word or term is historically derived in its etymology.
-
C.
etymology
Indicates the historical origin and development of a word or term, including its source language and form.
-
D.
etymologicalSource
Indicates that one term or name originates from, is derived from, or has its roots in another term or name.
-
E.
traditionalEtymology
Indicates that an entity’s origin or meaning is explained according to a historically established or customary etymological account.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b0ac8bc8190b4e4f79b15c316b3 |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:08 p.m.