Triple
T38062038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walther-Werke |
E950366
|
entity |
| Predicate | hasNamedEntity |
P201005
|
FINISHED |
| Object | Johann Gottfried Walther |
—
|
NE NERFINISHED |
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: Johann Gottfried Walther | Statement: [Walther-Werke, hasNamedEntity, Johann Gottfried Walther]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamedEntity Context triple: [Walther-Werke, hasNamedEntity, Johann Gottfried Walther]
-
A.
isNamedEntity
Indicates that the subject is recognized as a named entity, such as a specific person, organization, location, or other proper noun.
-
B.
hasNameEntityUsage
Indicates that an entity is associated with a particular usage or occurrence of a specific name.
-
C.
hasNamedForRole
Indicates that an entity has been given a specific name or label that corresponds to a particular role it plays.
-
D.
hasNaming
Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by another entity.
-
E.
hasNicknamedEntityType
Indicates that an entity is associated with another entity type specifically in the role of being its nickname or informal name.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
| PDg | Predicate description generation | batch_69ffc082a4e881908a92313d2c755afe |
completed | May 9, 2026, 11:17 p.m. |
Created at: May 3, 2026, 4:21 p.m.