Triple
T14933998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishkashimi |
E372341
|
entity |
| Predicate | hasNounInflection |
P75334
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ishkashimi, hasNounInflection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNounInflection Context triple: [Ishkashimi, hasNounInflection, yes]
-
A.
hasNounEnding
Indicates that something possesses or exhibits a particular noun-forming ending or suffix.
-
B.
hasNoun
Indicates that an entity possesses or is associated with a specific noun as an attribute, label, or grammatical component.
-
C.
inflectionOf
Indicates that one linguistic form is an inflected variant of another base or lemma form.
-
D.
hasNounClassSystem
Indicates that an entity possesses a grammatical system in which nouns are categorized into distinct classes that affect their agreement with other elements in the language.
-
E.
isInflectedLanguage
chosen
Indicates that a language uses systematic changes in word form (inflections) to express grammatical categories such as tense, case, number, or gender.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded646a0808190ba5c0c91bde011c5 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:37 a.m.