Triple
T29491778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 343 of the Constitution of India |
E748100
|
entity |
| Predicate | specifiesScript |
P150428
|
FINISHED |
| Object | Devanagari script for Hindi |
—
|
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: Devanagari script for Hindi | Statement: [Article 343 of the Constitution of India, specifiesScript, Devanagari script for Hindi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specifiesScript Context triple: [Article 343 of the Constitution of India, specifiesScript, Devanagari script for Hindi]
-
A.
usesScriptFor
chosen
Indicates that one entity employs or relies on a particular script or writing system for its representation, communication, or operation.
-
B.
appliesToScript
Indicates that something (such as a rule, configuration, or operation) is specifically relevant or applicable to a given script.
-
C.
scriptType
Indicates the classification or category of a script, specifying what kind of script it is (e.g., its format, purpose, or scripting language type).
-
D.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
-
E.
hasScriptBy
Indicates that one entity has its script authored, written, or created by another entity.
- 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_69f0bd448c6881908aa6b475cefd5ddc |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 4:14 p.m.