Triple
T1990053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thaana script |
E43230
|
entity |
| Predicate | hasStandardization |
P7508
|
FINISHED |
| Object | included in Unicode Standard |
—
|
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: included in Unicode Standard | Statement: [Thaana script, hasStandardization, included in Unicode Standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandardization Context triple: [Thaana script, hasStandardization, included in Unicode Standard]
-
A.
hasStandardizationEffort
Indicates that there is an organized effort or process to standardize something, such as practices, formats, or specifications, across relevant entities or contexts.
-
B.
hasStandardizationBody
Indicates that an entity is associated with, governed by, or defined by a specific standards-setting organization or authority.
-
C.
standardizationStatus
Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
-
D.
isStandardizationTargetOf
Indicates that an entity is the object or subject being standardized within a standardization process, activity, or initiative.
-
E.
standardizedIn
chosen
Indicates that something has been formally defined, regulated, or made uniform within a particular standard, framework, or jurisdiction.
- 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_69a88714cf2c819081644be450b8356e |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8ee02dc81908fec9fd8df7a4f40 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb79ad6888190be99943a9c73cf3e |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:37 p.m.