Triple
T31095233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudolfovich |
E792506
|
entity |
| Predicate | etymologicalRootNameOrigin |
P108324
|
FINISHED |
| Object | Germanic given name Rudolf |
—
|
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 name Rudolf | Statement: [Rudolfovich, etymologicalRootNameOrigin, Germanic given name Rudolf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologicalRootNameOrigin Context triple: [Rudolfovich, etymologicalRootNameOrigin, Germanic given name Rudolf]
-
A.
etymologicalRootName
chosen
Indicates that one name is derived from, or originates etymologically in, another name.
-
B.
etymologicalRootMeaning
Indicates that one term’s meaning originates from or is derived from the historical or original meaning of another term.
-
C.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
-
D.
possibleNameEtymology
Indicates a hypothesized or suggested origin or derivation of an entity’s name from another term, source, or linguistic root.
-
E.
hasNameEtymologyIn
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:03 p.m.