Triple
T4523712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhishma Parva |
E103325
|
entity |
| Predicate | textualDivision |
P22618
|
FINISHED |
| Object | contains the eighteen chapters of the Bhagavad Gita |
—
|
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: contains the eighteen chapters of the Bhagavad Gita | Statement: [Bhishma Parva, textualDivision, contains the eighteen chapters of the Bhagavad Gita]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textualDivision Context triple: [Bhishma Parva, textualDivision, contains the eighteen chapters of the Bhagavad Gita]
-
A.
textualStructure
chosen
Indicates how parts of a text are organized and related to each other within its overall structure.
-
B.
dividedBetween
Indicates that something is partitioned or shared among two or more distinct entities or groups.
-
C.
formsNaturalDivideBetween
Indicates that one entity serves as a natural boundary or separation between two other entities.
-
D.
divisionLine
Indicates a boundary or separating line that divides one area, group, or portion from another.
-
E.
textFragment
Indicates that one piece of text is a constituent part or segment of a larger text.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd574d7c2481909049955ca47613a6 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521cf77c819083852de3094d1377 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:03 p.m.