Triple
T27326472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hans Weber |
E689662
|
entity |
| Predicate | etymologyOfSurname |
P97319
|
FINISHED |
| Object | occupational name for a weaver |
—
|
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: occupational name for a weaver | Statement: [Hans Weber, etymologyOfSurname, occupational name for a weaver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologyOfSurname Context triple: [Hans Weber, etymologyOfSurname, occupational name for a weaver]
-
A.
hasSurnameEthymology
Indicates that an entity’s surname originates from, or is derived based on, a specified source, language, or etymological root.
-
B.
etymologyOfCognomen
chosen
Indicates that one term specifies the linguistic origin or derivation of a particular cognomen (surname or family name).
-
C.
nameEtymologyFor
Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
-
D.
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.
-
E.
languageOfSurnameVariants
Indicates the language in which particular surname variants are used or originate.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f627edd6d08190a059d44edecfb368 |
completed | May 2, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 11:36 a.m.