Triple
T18593757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhishmaparvan |
E454434
|
entity |
| Predicate | includesMilitaryNarrative |
P6847
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bhishmaparvan, includesMilitaryNarrative, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMilitaryNarrative Context triple: [Bhishmaparvan, includesMilitaryNarrative, yes]
-
A.
historicalNarrative
Indicates that one entity presents or constitutes a story or account about past events involving another entity.
-
B.
containsNarrativeOf
chosen
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
-
C.
hasMilitarySignificance
Indicates that something holds strategic or tactical importance for military planning, operations, or defense objectives.
-
D.
militaryConflictInBackstory
Indicates that a character or entity has a history involving a military conflict that occurred prior to the main events or timeline being described.
-
E.
militaryEventMentionedIn
Indicates that a specific military event is referenced or discussed within a particular document, text, or source.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b7ce3881908302ee27a2cf80d6 |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.