Triple
T17030305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gisbert |
E413175
|
entity |
| Predicate | etymologicalClass |
P125565
|
FINISHED |
| Object | Germanic given names |
—
|
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: Germanic given names | Statement: [Gisbert, etymologicalClass, Germanic given names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologicalClass Context triple: [Gisbert, etymologicalClass, Germanic given names]
-
A.
etymologicalRole
Indicates the specific function or contribution an element has within the historical origin and development of a word or term.
-
B.
etymologicalForm
Indicates that one linguistic form is derived from, or historically originates in, another form as its etymological source.
-
C.
etymologicalLanguage
Indicates the language from which a word or term is historically derived in its etymology.
-
D.
etymologyType
Indicates the specific kind or category of etymological relationship that links a term to its linguistic origin or source.
-
E.
etymologicalField
Indicates that one term belongs to a particular semantic or conceptual domain relevant to its etymological origin or historical development.
- F. None of above. chosen
Provenance (4 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d5d918ec8190b54c40c2a5e9b6b9 |
completed | April 18, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:33 a.m.