Triple
T11866176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elend (German) |
E282289
|
entity |
| Predicate | relatedAdjective |
P31789
|
FINISHED |
| Object | elend |
—
|
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: elend | Statement: [Elend (German), relatedAdjective, elend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedAdjective Context triple: [Elend (German), relatedAdjective, elend]
-
A.
associatedKeyword
Indicates that one entity is linked to or characterized by a particular keyword used for identification, categorization, or retrieval.
-
B.
relatedMorphologicalFeature
chosen
Indicates that one entity is connected to another through a shared or corresponding morphological feature or structure.
-
C.
moreCloselyRelatedTo
Indicates that one entity has a stronger or closer relationship, connection, or similarity to a second entity than to some other reference entity.
-
D.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
E.
semanticRelation
Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a73a233081909449ab294d01a512 |
completed | April 10, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69d8a2589f0c8190ad82ff11acabae93 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.