Triple
T19596899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naga kingdom |
E470369
|
entity |
| Predicate | relatedMythicGroup |
P118114
|
FINISHED |
| Object | Yaksha realms |
—
|
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: Yaksha realms | Statement: [Naga kingdom, relatedMythicGroup, Yaksha realms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedMythicGroup Context triple: [Naga kingdom, relatedMythicGroup, Yaksha realms]
-
A.
associatedMystic
Indicates a relationship where one entity is linked or connected to another through a mystical, spiritual, or esoteric association.
-
B.
sharesMythosWith
Indicates that two entities are associated with, or originate from, the same mythological tradition, narrative system, or shared set of myths.
-
C.
typeOfMythologicalGroup
Indicates that one entity is classified as a specific kind or category of mythological group to which the other entity belongs.
-
D.
relationshipWithOtherGroup
chosen
Indicates that one group has some defined connection, association, or interaction with another distinct group.
-
E.
associatedWithFictionalGroup
Indicates that an entity has a connection or affiliation with a fictional group, organization, or collective.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6407b997881909762c8f919c9cdad |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.