Triple
T9665462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilfy |
E233692
|
entity |
| Predicate | etymologicalRoot |
P453
|
FINISHED |
| Object |
GermanicNameWilfred
GermanicNameWilfred is a traditional Germanic given name meaning roughly “desiring peace” or “will for peace.”
|
E814191
|
NE FINISHED |
How this triple was built (4 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: GermanicNameWilfred | Statement: [Wilfy, etymologicalRoot, GermanicNameWilfred]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GermanicNameWilfred Context triple: [Wilfy, etymologicalRoot, GermanicNameWilfred]
-
A.
Wido (medieval Germanic name)
Wido is a medieval Germanic given name, related to forms like Guido and Guy, that was borne by various nobles and clerics in early European history.
-
B.
Germanic name Hrodebert
Germanic name Hrodebert is an old Germanic personal name meaning “bright fame,” from which various modern names like Robert and Robby ultimately originate.
-
C.
Wulfert
Wulfert is a surname of likely European origin associated with individuals such as Natalia Sergeyevna Wulfert.
-
D.
Wulfram
Wulfram is an alternative spelling or variant form of the name Wolfram, which is associated with both a given name and the chemical element tungsten.
-
E.
Cynewald
Cynewald was an early medieval Anglo-Saxon noble associated with the royal Iclingas dynasty of Mercia.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: GermanicNameWilfred Triple: [Wilfy, etymologicalRoot, GermanicNameWilfred]
Generated description
GermanicNameWilfred is a traditional Germanic given name meaning roughly “desiring peace” or “will for peace.”
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: GermanicNameWilfred Target entity description: GermanicNameWilfred is a traditional Germanic given name meaning roughly “desiring peace” or “will for peace.”
-
A.
Wido (medieval Germanic name)
Wido is a medieval Germanic given name, related to forms like Guido and Guy, that was borne by various nobles and clerics in early European history.
-
B.
Germanic name Hrodebert
Germanic name Hrodebert is an old Germanic personal name meaning “bright fame,” from which various modern names like Robert and Robby ultimately originate.
-
C.
Wulfert
Wulfert is a surname of likely European origin associated with individuals such as Natalia Sergeyevna Wulfert.
-
D.
Wulfram
Wulfram is an alternative spelling or variant form of the name Wolfram, which is associated with both a given name and the chemical element tungsten.
-
E.
Cynewald
Cynewald was an early medieval Anglo-Saxon noble associated with the royal Iclingas dynasty of Mercia.
- F. None of above. chosen
Provenance (5 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c38f65c8190a0ed20830249a0f1 |
completed | April 1, 2026, 10:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d18a1c8b188190bcff470244b21640 |
completed | April 4, 2026, 10:01 p.m. |
| NEDg | Description generation | batch_69d18b0929788190955f0da0eadb3210 |
completed | April 4, 2026, 10:04 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d18ea5ffbc8190b336c98087838d7b |
completed | April 4, 2026, 10:20 p.m. |
Created at: March 30, 2026, 8:14 p.m.