Triple
T4519991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nala and Damayanti |
E103241
|
entity |
| Predicate | functionInEpic |
P46726
|
FINISHED |
| Object | consolation narrative for the Pandavas in exile |
—
|
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: consolation narrative for the Pandavas in exile | Statement: [Nala and Damayanti, functionInEpic, consolation narrative for the Pandavas in exile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInEpic Context triple: [Nala and Damayanti, functionInEpic, consolation narrative for the Pandavas in exile]
-
A.
functionInWork
chosen
Indicates that a particular function, role, or operation is performed, utilized, or occurs within the context of a specific work or creation.
-
B.
functionInName
Indicates that the name of one entity includes or references the function or role of another entity.
-
C.
functionInSystem
Indicates that an entity serves a specific role or performs a particular function within a given system.
-
D.
intendedFunction
Indicates that something is designed or purposed to perform a particular role, use, or function.
-
E.
publicFunction
Indicates that a function or method is accessible from outside its defining scope, module, or class (i.e., it has public visibility).
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5747e90c81908fa112ecace699a9 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521abea48190b3e758a1f98dd55e |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.