Triple

T4513088
Position Surface form Disambiguated ID Type / Status
Subject Hindu lunisolar calendar E102093 entity
Predicate historicalOriginApprox P1614 FINISHED
Object 1st millennium BCE 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: 1st millennium BCE | Statement: [Hindu lunisolar calendar, historicalOriginApprox, 1st millennium BCE]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalOriginApprox
Context triple: [Hindu lunisolar calendar, historicalOriginApprox, 1st millennium BCE]
  • A. historicalOrigin
    Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
  • B. hasHistoricalOrigin chosen
    Indicates that something originated, was first established, or came into existence during a specific historical period or context.
  • C. historicalOriginCountry
    Indicates the country from which something originally came or first emerged in a historical context.
  • D. historicallyBorneBy
    Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
  • E. historicalBackground
    Indicates that one entity provides contextual historical information or circumstances that help explain the origin, development, or significance of another entity.
  • 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_69bd43d6251c81909deecce3e6e9d69c completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd5722d8fc81909c5f2d9a38d17a6b completed March 20, 2026, 2:18 p.m.
PD Predicate disambiguation batch_69bd5218afb4819087c99e0a1f22e137 completed March 20, 2026, 1:56 p.m.
Created at: March 20, 2026, 1:02 p.m.