Triple
T4996080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Gondi |
E112248
|
entity |
| Predicate | hasScriptDevelopment |
P2224
|
FINISHED |
| Object | community-based orthographies |
—
|
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: community-based orthographies | Statement: [Southern Gondi, hasScriptDevelopment, community-based orthographies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScriptDevelopment Context triple: [Southern Gondi, hasScriptDevelopment, community-based orthographies]
-
A.
scriptDevelopedFor
Indicates that a script was specifically created or developed for use by, or in the context of, a particular entity or purpose.
-
B.
hasEditorScripting
Indicates that an entity provides or supports scripting capabilities specifically for editing or editor-related functionality.
-
C.
scriptDevelopedBy
Indicates that a script (such as a screenplay or written program) was created or authored by a particular person or entity.
-
D.
hasDevelopmentType
chosen
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
-
E.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
- 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_69bd4432b32c81909f3b3c6bd10f0653 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd714aee2481908fb0dd5fa2daf3a1 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.