Triple

T18737922
Position Surface form Disambiguated ID Type / Status
Subject Sanjaya and Dhritarashtra E458211 entity
Predicate narrativeRelationship P104581 FINISHED
Object narrator–listener 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: narrator–listener | Statement: [Sanjaya and Dhritarashtra, narrativeRelationship, narrator–listener]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: narrativeRelationship
Context triple: [Sanjaya and Dhritarashtra, narrativeRelationship, narrator–listener]
  • A. fictionalRelationship
    Indicates a relationship that exists only within a fictional or imagined context between entities.
  • B. literaryRelationship
    Indicates a relationship between entities that are connected through literature, such as authorship, influence, adaptation, or other text-based associations.
  • C. relationshipStatusInStory chosen
    Indicates the type or state of the relationship between entities as it exists within the context of a specific story or narrative.
  • D. portraysRelationship
    Indicates that one entity depicts, represents, or illustrates a relationship between other entities.
  • E. historicalRelationship
    Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
  • 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_69d8d394dc308190b6725073f5db324c completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5768b80ac8190bc05628d64f86fc9 completed April 20, 2026, 12:42 a.m.
PD Predicate disambiguation batch_69e48d03766c8190a43f7681842f4f8d completed April 19, 2026, 8:06 a.m.
Created at: April 10, 2026, 11:51 a.m.