Triple

T19882723
Position Surface form Disambiguated ID Type / Status
Subject Angiras E477818 entity
Predicate lineageInfluence P115355 FINISHED
Object several Brahmin gotras trace origin to Angiras 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: several Brahmin gotras trace origin to Angiras | Statement: [Angiras, lineageInfluence, several Brahmin gotras trace origin to Angiras]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lineageInfluence
Context triple: [Angiras, lineageInfluence, several Brahmin gotras trace origin to Angiras]
  • A. lineageRelatedTo
    Indicates a relationship where two entities are connected through a line of descent or ancestry within the same lineage.
  • B. lineageSystem
    Indicates a hierarchical ancestry or descent relationship that traces how entities are derived from or originate through one another within a system.
  • C. heritageLine
    Indicates that one entity is a historical or traditional predecessor, lineage, or source from which the other entity derives or continues.
  • D. sourceOfLineageFor chosen
    Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
  • E. lineageConcept
    Indicates a conceptual or abstract relationship of lineage, such as ancestry or descent, between entities.
  • 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_69d8e51f32b08190b3687f4f60353250 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e658e0ccc88190b6f093035cd6f2a1 completed April 20, 2026, 4:48 p.m.
PD Predicate disambiguation batch_69e537e8c4e481909fe95d795b4864e7 completed April 19, 2026, 8:15 p.m.
Created at: April 10, 2026, 1:52 p.m.