Triple

T17951251
Position Surface form Disambiguated ID Type / Status
Subject Shachi E448835 entity
Predicate hasConsortRole P129864 FINISHED
Object chief consort of Indra 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: chief consort of Indra | Statement: [Shachi, hasConsortRole, chief consort of Indra]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasConsortRole
Context triple: [Shachi, hasConsortRole, chief consort of Indra]
  • A. hasCompanionRoleIn
    Indicates that an entity serves in a companion or supporting role within a specified context, activity, or relationship.
  • B. hasPartnershipRole
    Indicates that an entity holds a specific role or function within a partnership relationship with another entity.
  • C. hasCoRepresentativeRole
    Indicates that an entity shares or holds a co-representative role or position alongside another entity within the same representational context.
  • D. hasEnsembleRoleWith
    Indicates that two or more entities share a collaborative or joint role within the same ensemble, group, or collective context.
  • E. consensusRole
    Indicates that an entity participates in a consensus process with a specific functional role (e.g., proposer, validator, leader, or follower) within that agreement mechanism.
  • F. None of above. chosen

Provenance (4 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_69d8b9f8cca8819099836916c56b7c95 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4afac95048190a5d1ef012899c62b completed April 19, 2026, 10:34 a.m.
PD Predicate disambiguation batch_69e3f8f2bd088190b1e22ad4d9cc8b13 completed April 18, 2026, 9:34 p.m.
PDg Predicate description generation batch_69e42d8d68288190a05dc5d7803cf823 completed April 19, 2026, 1:19 a.m.
Created at: April 10, 2026, 10:21 a.m.