Triple
T37471579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyrian (language) |
E931165
|
entity |
| Predicate | hasCanonicalGrammar |
P18535
|
FINISHED |
| Object | unknown or limited |
—
|
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: unknown or limited | Statement: [Kyrian (language), hasCanonicalGrammar, unknown or limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalGrammar Context triple: [Kyrian (language), hasCanonicalGrammar, unknown or limited]
-
A.
hasGrammar
Indicates that an entity possesses, follows, or is associated with a particular system of grammatical rules or structure.
-
B.
hasGrammarFrom
Indicates that one entity derives or uses its grammatical structure or rules from another entity.
-
C.
hasKnownGrammar
chosen
Indicates that an entity is associated with a grammar whose structure and rules are already defined or understood.
-
D.
hasGrammarInformation
Indicates that an entity is associated with specific grammatical details or annotations, such as part of speech, inflection, or syntactic properties.
-
E.
hasCanonicalRecognition
Indicates that an entity is officially acknowledged or accepted as authoritative or standard within a recognized canon or formal framework.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00119d821c8190874786391b27ef23 |
completed | May 10, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a001143fb6881909ac0ae8bfea04351 |
completed | May 10, 2026, 5:01 a.m. |
Created at: May 3, 2026, 4:17 p.m.