Triple

T25230492
Position Surface form Disambiguated ID Type / Status
Subject Pallava architecture E632206 entity
Predicate pioneeredFeature P80871 FINISHED
Object transition from rock-cut to structural temples 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: transition from rock-cut to structural temples | Statement: [Pallava architecture, pioneeredFeature, transition from rock-cut to structural temples]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: pioneeredFeature
Context triple: [Pallava architecture, pioneeredFeature, transition from rock-cut to structural temples]
  • A. pioneeringAspect
    Indicates that something embodies an innovative, trailblazing, or first-of-its-kind quality within a particular domain or context.
  • B. technologyPioneered
    Indicates that an entity was the first or among the first to develop, introduce, or significantly advance a particular technology.
  • C. innovativeFeature
    Indicates that an entity possesses or introduces a novel, advanced, or uniquely improved feature compared to existing alternatives.
  • D. introducedFeatureCategory chosen
    Indicates that an entity caused a particular feature category to be created, presented, or made available for the first time.
  • E. documentedFeature
    Indicates that a feature has been formally recorded or described in documentation.
  • 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_69e75a8e0f688190a7aebe9a4815e25b completed April 21, 2026, 11:07 a.m.
NER Named-entity recognition batch_69f47cc7199c8190bf32bd5aa0090e07 completed May 1, 2026, 10:13 a.m.
PD Predicate disambiguation batch_69f44d849e7c81909945438f40e35362 completed May 1, 2026, 6:51 a.m.
Created at: April 21, 2026, 1:04 p.m.