Triple
T6646398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lule Sami language |
E150710
|
entity |
| Predicate | hasInflectionalMorphology |
P7162
|
FINISHED |
| Object | rich |
—
|
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 | Statement: [Lule Sami language, hasInflectionalMorphology, rich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInflectionalMorphology Context triple: [Lule Sami language, hasInflectionalMorphology, rich]
-
A.
inflectionOf
Indicates that one linguistic form is an inflected variant of another base or lemma form.
-
B.
hasInfinitive
Indicates that one entity is associated with the infinitive form of a verb represented by the other entity.
-
C.
hasVerbalFeature
Indicates that an entity possesses a specific verbal property, characteristic, or behavior related to speech or language.
-
D.
hasLinguisticFeature
chosen
Indicates that an entity possesses a particular linguistic property, trait, or characteristic.
-
E.
hasInfinitiveVerbEnding
Indicates that a verb takes the infinitive form with a specific infinitive verb ending (such as “-to” in English or “-en” in German).
- 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad04d66c8190926ffcbff372643b |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2 p.m.