Triple
T1083481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nepali |
E23998
|
entity |
| Predicate | usedInLiterature |
P7826
|
FINISHED |
| Object | modern Nepali 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: modern Nepali literature | Statement: [Nepali, usedInLiterature, modern Nepali literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInLiterature Context triple: [Nepali, usedInLiterature, modern Nepali literature]
-
A.
literarySource
Indicates that one entity serves as the written or literary origin, reference, or basis for another entity.
-
B.
hasLiterarySignificance
Indicates that something holds notable importance, influence, or value within the realm of literature or literary studies.
-
C.
usedInCulture
chosen
Indicates that something (such as an object, practice, or concept) is employed, referenced, or plays a role within a particular culture or cultural context.
-
D.
literaryInfluence
Indicates that one entity has had a significant impact on the style, themes, or development of another entity’s literary work.
-
E.
literaryFeature
Indicates a relationship where something possesses or exhibits a characteristic, device, or stylistic element used in literature.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b95e56948190a1e92367ad7240b7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73f4310819086281f8ec67d1a32 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.