Triple
T4533406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuru dynasty |
E106349
|
entity |
| Predicate | roleInEpic |
P42552
|
FINISHED |
| Object | central ruling house in the Mahabharata narrative |
—
|
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: central ruling house in the Mahabharata narrative | Statement: [Kuru dynasty, roleInEpic, central ruling house in the Mahabharata narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInEpic Context triple: [Kuru dynasty, roleInEpic, central ruling house in the Mahabharata narrative]
-
A.
roleInIntegration
Indicates the specific function or responsibility an entity has within a combined or coordinated system, process, or integration.
-
B.
roleInStories
chosen
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
C.
roleInEngine
Indicates the specific function or responsibility an entity has within an engine or engine-like system.
-
D.
plannedRole
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
-
E.
roleInToolchain
Indicates that an entity serves a specific function or position within a larger sequence of tools or processes in a toolchain.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57a08ec4819091b84d53d7b564a7 |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521edd00819099dfccaa65dddd61 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:04 p.m.