Triple
T21137460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newa |
E520848
|
entity |
| Predicate | supportsNuktaLikeMarks |
P18518
|
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: [Newa, supportsNuktaLikeMarks, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNuktaLikeMarks Context triple: [Newa, supportsNuktaLikeMarks, true]
-
A.
hasNuktaLikeSigns
chosen
Indicates that one element possesses or includes diacritic marks that are similar in form or function to nukta signs.
-
B.
hasAnusvaraLikeSign
Indicates that one entity possesses or uses a diacritic or mark functionally similar to an anusvara sign in writing or notation.
-
C.
supportsNasalizationMarking
Indicates that a system or element provides for the representation or marking of nasalization in its notation or structure.
-
D.
usesToneMarks
Indicates that one entity applies or includes diacritical tone marks in the representation or transcription of another entity (such as text, language, or symbols).
-
E.
hasCombiningMarks
Indicates that an entity (such as a character or string) includes one or more combining marks attached to a base element.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7235b89188190a6209c0a1839ee03 |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:57 p.m.