Triple
T4906505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bharata |
E109923
|
entity |
| Predicate | requestedOfRama |
P34717
|
FINISHED |
| Object | return to Ayodhya and accept the throne |
—
|
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: return to Ayodhya and accept the throne | Statement: [Bharata, requestedOfRama, return to Ayodhya and accept the throne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requestedOfRama Context triple: [Bharata, requestedOfRama, return to Ayodhya and accept the throne]
-
A.
requestedBy
Indicates that one entity has made a request for something to be done, provided, or obtained by another entity.
-
B.
requestedFrom
chosen
Indicates that one entity has made a request to another entity as the source or provider of something.
-
C.
requisitionedBy
Indicates that something has been formally requested or claimed for official use by a particular agent or authority.
-
D.
mayRequest
Indicates that one entity is permitted or authorized to make a request to another entity or for a particular resource or action.
-
E.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
- 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_69bd441180708190ba42ffb44fea533a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e72ed5c819081104c99a398e0af |
completed | March 20, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.