Triple
T1194376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indo-Iranian languages |
E25632
|
entity |
| Predicate | includesClassicalLanguage |
P2177
|
FINISHED |
| Object | Sanskrit |
—
|
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: Sanskrit | Statement: [Indo-Iranian languages, includesClassicalLanguage, Sanskrit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesClassicalLanguage Context triple: [Indo-Iranian languages, includesClassicalLanguage, Sanskrit]
-
A.
mainClassicalLanguage
Indicates the primary classical (historically foundational) language associated with an entity, such as a text, culture, or scholarly tradition.
-
B.
recognizedAsClassicalLanguageBy
Indicates that an entity is acknowledged or designated by a specified authority or source as a classical language.
-
C.
ancientLanguages
Indicates that the related entities are languages that originated in and were used during ancient historical periods.
-
D.
includesLanguage
chosen
Indicates that one entity contains, supports, or makes use of a specified language as part of its content, functionality, or representation.
-
E.
linguisticClassification
Indicates the relationship by which an entity is categorized according to its language or linguistic type.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd7743548190a70d3f3c7378aaa7 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.