Triple
T19741919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laxman Kumara |
E474143
|
entity |
| Predicate | relationshipToDuryodhana |
P131685
|
FINISHED |
| Object | only son in many retellings |
—
|
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: only son in many retellings | Statement: [Laxman Kumara, relationshipToDuryodhana, only son in many retellings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToDuryodhana Context triple: [Laxman Kumara, relationshipToDuryodhana, only son in many retellings]
-
A.
relationshipToKauravas
chosen
Indicates the type or nature of a person's familial or social relationship to the Kauravas.
-
B.
relationshipWithBharata
Indicates that there exists a specific type of relationship or association between an entity and Bharata.
-
C.
relationshipToTheDude
Indicates the specific type of personal or social relationship that one entity has to the individual referred to as "the Dude."
-
D.
intraVedicRelation
Indicates a relationship that connects elements within the Vedic corpus itself, such as links between Vedic texts, concepts, or traditions.
-
E.
relationshipToPriam
Indicates a familial or social connection that someone has specifically with Priam.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65162382081909bd5a251d7da7f75 |
completed | April 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.