Triple
T15609348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helmold |
E375244
|
entity |
| Predicate | isComposedOfMorphemes |
P106688
|
FINISHED |
| Object | helm + wald |
—
|
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: helm + wald | Statement: [Helmold, isComposedOfMorphemes, helm + wald]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isComposedOfMorphemes Context triple: [Helmold, isComposedOfMorphemes, helm + wald]
-
A.
containsMorpheme
chosen
Indicates that one linguistic unit (such as a word or stem) includes a particular morpheme as one of its meaningful subparts.
-
B.
morphologicalComplexity
Indicates the degree to which a language’s word forms are structurally intricate, involving multiple morphemes, inflections, or derivational processes.
-
C.
compositionalForm
Indicates the structural or formal composition that defines how parts are organized or combined within something.
-
D.
hasVerbalMorphology
Indicates that one linguistic element exhibits verbal inflectional properties or patterns in relation to another.
-
E.
hasSyllabary
Indicates that one entity possesses or is associated with a specific syllabary writing system used to represent its language or notation.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e8024948190a6c711f2e5c2aac4 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:13 a.m.