Triple
T31806284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khwarezmian script |
E811879
|
entity |
| Predicate | graphemicNature |
P145337
|
FINISHED |
| Object | consonant-based |
—
|
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: consonant-based | Statement: [Khwarezmian script, graphemicNature, consonant-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graphemicNature Context triple: [Khwarezmian script, graphemicNature, consonant-based]
-
A.
graphemicUnit
Indicates a relationship where one element functions as a basic written symbol or character unit within a writing system.
-
B.
graphemeInventory
Indicates the set of distinct written symbols or characters used in a language or writing system.
-
C.
glottographicType
chosen
Indicates the type or nature of a writing or script system used to represent language glottographically.
-
D.
hasGraphemeToPhonemeRelation
Indicates a relationship where a written symbol or sequence of symbols (grapheme) is systematically associated with a corresponding sound or sequence of sounds (phoneme).
-
E.
characterFormationMethod
Indicates the process or technique by which a character is created, developed, or brought into existence.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:42 p.m.