Triple
T7257387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kambera language |
E157754
|
entity |
| Predicate | hasNominalMorphology |
P75599
|
FINISHED |
| Object | limited case marking |
—
|
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: limited case marking | Statement: [Kambera language, hasNominalMorphology, limited case marking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNominalMorphology Context triple: [Kambera language, hasNominalMorphology, limited case marking]
-
A.
morphologicalClass
Indicates the classification of an entity based on its morphological form or structural pattern.
-
B.
notableMorphology
Indicates that an entity is characterized by a distinctive or noteworthy physical form, structure, or shape.
-
C.
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.
-
D.
hasNounEnding
Indicates that something possesses or exhibits a particular noun-forming ending or suffix.
-
E.
hasGrammaticalNumber
Indicates that an expression is associated with a specific grammatical number category (such as singular, plural, or dual) in a language.
- F. None of above. chosen
Provenance (4 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6eaa3d88081908f59ca5a85790290 |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6e889854481908c765ce2107f2d3a |
completed | March 27, 2026, 8:28 p.m. |
Created at: March 27, 2026, 2:57 p.m.