Triple
T20053018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Jinheung |
E499251
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object |
Queen Maya
Queen Maya was a royal consort of the Silla kingdom in ancient Korea, known primarily as the wife of King Jinheung.
|
E1408495
|
NE FINISHED |
How this triple was built (4 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: Queen Maya | Statement: [King Jinheung, spouse, Queen Maya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Queen Maya Context triple: [King Jinheung, spouse, Queen Maya]
-
A.
Queen Maya Devi
Queen Maya Devi is revered in Buddhist tradition as the mother of Siddhartha Gautama, who became the Buddha.
-
B.
Māyā
Māyā is the mother of Siddhartha Gautama (the Buddha) in Buddhist tradition, revered as Queen Māyādevī.
-
C.
Queen Kausalya
Queen Kausalya is a revered figure in Hindu tradition, known as the chief consort of King Dasharatha and the mother of Lord Rama in the epic Ramayana.
-
D.
Lalita
Lalita is a revered aspect of the Hindu goddess Devi, celebrated as a beautiful, benevolent, and playful form of the Divine Mother often associated with Sri Vidya worship.
-
E.
Queen of Hastinapura
The Queen of Hastinapura is a royal consort in the Kuru dynasty of the Indian epic Mahabharata, most prominently associated with Kunti, the mother of the Pandavas.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Queen Maya Triple: [King Jinheung, spouse, Queen Maya]
Generated description
Queen Maya was a royal consort of the Silla kingdom in ancient Korea, known primarily as the wife of King Jinheung.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Queen Maya Target entity description: Queen Maya was a royal consort of the Silla kingdom in ancient Korea, known primarily as the wife of King Jinheung.
-
A.
Queen Maya Devi
Queen Maya Devi is revered in Buddhist tradition as the mother of Siddhartha Gautama, who became the Buddha.
-
B.
Māyā
Māyā is the mother of Siddhartha Gautama (the Buddha) in Buddhist tradition, revered as Queen Māyādevī.
-
C.
Queen Kausalya
Queen Kausalya is a revered figure in Hindu tradition, known as the chief consort of King Dasharatha and the mother of Lord Rama in the epic Ramayana.
-
D.
Lalita
Lalita is a revered aspect of the Hindu goddess Devi, celebrated as a beautiful, benevolent, and playful form of the Divine Mother often associated with Sri Vidya worship.
-
E.
Queen of Hastinapura
The Queen of Hastinapura is a royal consort in the Kuru dynasty of the Indian epic Mahabharata, most prominently associated with Kunti, the mother of the Pandavas.
- F. None of above. chosen
Provenance (5 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6633043a481908359ad232607182a |
completed | April 20, 2026, 5:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a08160a013c81908ef326ebb9140803 |
completed | May 16, 2026, 7 a.m. |
| NEDg | Description generation | batch_6a0816d3c71081909138d3144a108266 |
completed | May 16, 2026, 7:03 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a08179df70c81908ea5bc596a8ba756 |
completed | May 16, 2026, 7:07 a.m. |
Created at: April 11, 2026, 3:38 p.m.