Triple
T4906506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bharata |
E109923
|
entity |
| Predicate | acceptedFromRama |
P57100
|
FINISHED |
| Object | instruction to rule as representative |
—
|
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: instruction to rule as representative | Statement: [Bharata, acceptedFromRama, instruction to rule as representative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptedFromRama Context triple: [Bharata, acceptedFromRama, instruction to rule as representative]
-
A.
acceptedIn
Indicates that something has been formally received, approved, or admitted into a particular context, group, or system.
-
B.
acceptedPramana
chosen
Indicates that one entity has acknowledged and accepted another entity as a valid source of knowledge or authority.
-
C.
approvedAs
Indicates that one entity has been officially accepted, authorized, or validated in a particular role, status, or capacity by another entity.
-
D.
recipientDecision
Indicates that a designated recipient makes or has made a choice or judgment regarding a proposal, request, or item.
-
E.
approvedAt
Indicates the date and time at which an entity received formal approval.
- 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.