Triple
T19406633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kushika dynasty |
E485478
|
entity |
| Predicate | textualNature |
P134238
|
FINISHED |
| Object | known primarily from Sanskrit literature |
—
|
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: known primarily from Sanskrit literature | Statement: [Kushika dynasty, textualNature, known primarily from Sanskrit literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textualNature Context triple: [Kushika dynasty, textualNature, known primarily from Sanskrit literature]
-
A.
textualCharacterization
chosen
Indicates that one entity provides a descriptive or narrative characterization of another entity, typically in textual form.
-
B.
textualStructure
Indicates how parts of a text are organized and related to each other within its overall structure.
-
C.
textuallySystematizedBy
Indicates that information, concepts, or data are organized, structured, or codified into a systematic textual form by a particular agent or source.
-
D.
textType
Indicates the classification of a text according to its type, format, or genre.
-
E.
textBy
Indicates that a given text or written content was authored or produced by a particular 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6257bad0c819088dd7729b6a36a94 |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:36 p.m.