Triple
T34503943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vivaha Panchami |
E885830
|
entity |
| Predicate | linkedMythologicalKingdom |
P83718
|
FINISHED |
| Object | Ayodhya |
—
|
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: Ayodhya | Statement: [Vivaha Panchami, linkedMythologicalKingdom, Ayodhya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedMythologicalKingdom Context triple: [Vivaha Panchami, linkedMythologicalKingdom, Ayodhya]
-
A.
linkedToMythology
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
B.
relatedMythicalPlace
chosen
Indicates that one entity has an association or connection with a mythical or legendary place in relation to the other entity.
-
C.
mentionsKingdom
Indicates that one entity explicitly refers to or brings up the topic of a kingdom in relation to another entity.
-
D.
mythologicalCapital
Indicates that a location serves as the principal or central city associated with a particular mythology or pantheon.
-
E.
kingdomAssociatedWith
Indicates a relationship where something is connected or related to a particular kingdom, such as belonging to, originating from, or being governed by that kingdom.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: May 1, 2026, 2:01 a.m.