Triple
T26135810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adbhut Ramayana (Assamese adaptation) |
E659377
|
entity |
| Predicate | hasSecondaryDeity |
P180200
|
FINISHED |
| Object | Sita |
—
|
NE NERFINISHED |
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: Sita | Statement: [Adbhut Ramayana (Assamese adaptation), hasSecondaryDeity, Sita]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryDeity Context triple: [Adbhut Ramayana (Assamese adaptation), hasSecondaryDeity, Sita]
-
A.
hasSiblingDeity
Indicates that one deity is a sibling (sharing at least one parent) of another deity.
-
B.
hasConsortDeity
Indicates that one deity is the consort (spouse or intimate divine partner) of another deity.
-
C.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
D.
hasParentDeity
Indicates that one deity is the parent (progenitor or creator) of another deity.
-
E.
hasNumberOfDeities
Indicates the specific count of deities associated with an entity, such as a religion, mythology, or belief system.
- F. None of above. chosen
Provenance (4 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
| PDg | Predicate description generation | batch_69f739a58b3c81908abc2b8738a65678 |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 26, 2026, 8:17 p.m.