Triple
T3232210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henrik |
E67764
|
entity |
| Predicate | hasComponentMorpheme |
P7161
|
FINISHED |
| Object | heim (home) |
—
|
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: heim (home) | Statement: [Henrik, hasComponentMorpheme, heim (home)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentMorpheme Context triple: [Henrik, hasComponentMorpheme, heim (home)]
-
A.
hasRootWord
Indicates that one linguistic form is derived from, based on, or directly associated with a specified root word.
-
B.
hasLinguisticElement
chosen
Indicates that one entity includes, is associated with, or is characterized by a particular linguistic component such as a word, phrase, symbol, or other language element.
-
C.
hasPhoneme
Indicates that a linguistic unit (such as a word or morpheme) contains or includes a particular phoneme as part of its sound structure.
-
D.
hasComponentSurname
Indicates that an entity’s full name includes a specified surname as one of its component parts.
-
E.
hasMorphologicalType
Indicates that an entity possesses or is classified by a particular morphological type or structural form.
- 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_69ad858c61888190a31196310d9b30b5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaed99d2c8190950fa883ec6f1f8e |
completed | March 8, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0dc2248190a38c40f4e06cd41c |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:08 p.m.