Triple
T10443743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cham script |
E246231
|
entity |
| Predicate | hasViramaLikeSign |
P16503
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cham script, hasViramaLikeSign, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViramaLikeSign Context triple: [Cham script, hasViramaLikeSign, true]
-
A.
hasViramaSign
Indicates that a character or script element is associated with, or takes, a virama sign used to suppress the inherent vowel in abugida writing systems.
-
B.
hasVirama
chosen
Indicates that a character or script element is associated with a virama sign, typically used to suppress the inherent vowel or join consonants in abugida writing systems.
-
C.
hasVisargaLikeSign
Indicates that one entity bears or includes a visarga-like diacritic or sign in relation to another entity.
-
D.
hasAnusvaraLikeSign
Indicates that one entity possesses or uses a diacritic or mark functionally similar to an anusvara sign in writing or notation.
-
E.
hasNuktaLikeSigns
Indicates that one element possesses or includes diacritic marks that are similar in form or function to nukta signs.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe083cd881909d2d8ad75d1d94cb |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb73a5e48190a8df4775bc5da80f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:15 p.m.