Triple
T31892789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GermanicNameWilfred |
E814191
|
entity |
| Predicate | hasComponentFromProtoGermanic |
P204132
|
FINISHED |
| Object | *wilja- |
—
|
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: *wilja- | Statement: [GermanicNameWilfred, hasComponentFromProtoGermanic, *wilja-]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentFromProtoGermanic Context triple: [GermanicNameWilfred, hasComponentFromProtoGermanic, *wilja-]
-
A.
equivalentInProtoGermanic
Indicates that two linguistic elements are considered to have the same or corresponding form or function in Proto-Germanic.
-
B.
hasLinguisticHeritage
Indicates that one entity possesses or is associated with the linguistic background, tradition, or ancestry of another entity.
-
C.
hasSorbianName
Indicates that an entity has a name or designation expressed in the Sorbian language.
-
D.
hasLatinEtymology
Indicates that something originates from or is derived from a Latin word or linguistic root.
-
E.
hasDialectalOriginOf
Indicates that something originates from or is derived from a particular dialect.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a033029023481909d9fa4a76b954879 |
completed | May 12, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_6a032d9f1fa48190bd1c94a8f930d02c |
completed | May 12, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_6a03302857c08190a5844ba27b152218 |
completed | May 12, 2026, 1:50 p.m. |
Created at: April 30, 2026, 11:58 p.m.