Triple
T6696264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samoyedic languages |
E152757
|
entity |
| Predicate | areMorphologically |
P48546
|
FINISHED |
| Object | rich in case system |
—
|
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: rich in case system | Statement: [Samoyedic languages, areMorphologically, rich in case system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areMorphologically Context triple: [Samoyedic languages, areMorphologically, rich in case system]
-
A.
notableMorphology
chosen
Indicates that an entity is characterized by a distinctive or noteworthy physical form, structure, or shape.
-
B.
modifiesMorphologyOf
Indicates that one entity alters or changes the morphological structure or form of another entity.
-
C.
relatedMorphologicalFeature
Indicates that one entity is connected to another through a shared or corresponding morphological feature or structure.
-
D.
morphologicalClass
Indicates the classification of an entity based on its morphological form or structural pattern.
-
E.
inflectionOf
Indicates that one linguistic form is an inflected variant of another base or lemma 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_69c6880687b08190805278b504d1c92c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6b5ed99e48190970805225458ce82 |
completed | March 27, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0e1d348190af1762ea1951038e |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:05 p.m.