Triple
T25451367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhattiprolu script |
E637789
|
entity |
| Predicate | hasGlyphCharacteristic |
P99801
|
FINISHED |
| Object | simplified consonant shapes |
—
|
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: simplified consonant shapes | Statement: [Bhattiprolu script, hasGlyphCharacteristic, simplified consonant shapes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlyphCharacteristic Context triple: [Bhattiprolu script, hasGlyphCharacteristic, simplified consonant shapes]
-
A.
hasGlyphsFor
Indicates that one entity provides or contains the necessary glyphs or visual symbols to represent another entity.
-
B.
hasGlyphRepertoireSize
Indicates the number of distinct glyphs included in an entity’s glyph repertoire.
-
C.
hasVisualCharacter
chosen
Indicates that one entity possesses or exhibits a particular visual appearance, style, or graphical characteristic defined by another entity.
-
D.
hasStyleCharacteristics
Indicates that one entity exhibits or embodies the stylistic features, traits, or qualities associated with another entity.
-
E.
hasCalligraphyLanguage
Indicates that an entity’s calligraphy is written in, or associated with, a particular language.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f707c8408190b0405250a2c02a03 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:03 p.m.