Triple
T19471758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boehkhʼul |
E487138
|
entity |
| Predicate | hasStandardGrammar |
P69032
|
FINISHED |
| Object | codified Avar grammar |
—
|
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: codified Avar grammar | Statement: [Boehkhʼul, hasStandardGrammar, codified Avar grammar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandardGrammar Context triple: [Boehkhʼul, hasStandardGrammar, codified Avar grammar]
-
A.
hasStandardizedGrammar
chosen
Indicates that a language or notation follows an officially defined and consistently applied set of grammatical rules.
-
B.
hasGrammar
Indicates that an entity possesses, follows, or is associated with a particular system of grammatical rules or structure.
-
C.
hasKnownGrammar
Indicates that an entity is associated with a grammar whose structure and rules are already defined or understood.
-
D.
hasDocumentedGrammars
Indicates that there exist written or otherwise formally recorded grammars describing the linguistic structure of the subject language or linguistic system.
-
E.
hasGrammarInformation
Indicates that an entity is associated with specific grammatical details or annotations, such as part of speech, inflection, or syntactic properties.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633e8d9188190a4939f03bad89add |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.