Triple
T9785391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirat Mundhum |
E237479
|
entity |
| Predicate | sacredTextForm |
P1184
|
FINISHED |
| Object | oral scripture |
—
|
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: oral scripture | Statement: [Kirat Mundhum, sacredTextForm, oral scripture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacredTextForm Context triple: [Kirat Mundhum, sacredTextForm, oral scripture]
-
A.
sacredTextStatus
Indicates the status or classification of a text in terms of its recognized sacredness or religious authority within a tradition.
-
B.
hasSacredText
chosen
Indicates that an entity possesses or is associated with a particular sacred or religious text.
-
C.
textSourceApocrypha
Indicates that the referenced text originates from or is classified as apocryphal writings.
-
D.
canonicalText
Indicates that a standardized, authoritative textual representation is associated with an entity or expression.
-
E.
traditionalText
Indicates that the associated text is expressed in a traditional or historically established form, style, or script as opposed to a modern or simplified variant.
- 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_69ca84da927881909bda80caecad6010 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda1b8b0a481909d9f7a25881d53be |
completed | April 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69cd03d77c6c81909b675955bf113320 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:27 p.m.