Triple

T24338319
Position Surface form Disambiguated ID Type / Status
Subject Patil E613442 entity
Predicate hasHistoricalMeaning P155766 FINISHED
Object village headman 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: village headman | Statement: [Patil, hasHistoricalMeaning, village headman]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricalMeaning
Context triple: [Patil, hasHistoricalMeaning, village headman]
  • A. hasHistoricalSignificance
    Indicates that something possesses notable importance or influence within a historical context or period.
  • B. hasHistoricSignificanceFor
    Indicates that something holds notable historical importance or relevance for a particular entity or group.
  • C. hasHistoricalOrigin
    Indicates that something originated, was first established, or came into existence during a specific historical period or context.
  • D. hasHistoricalSignificanceThrough
    Indicates that one entity possesses historical importance or relevance by means of, or as established through, its connection or association with another entity or event.
  • E. hasHistoricalContext
    Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
  • 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_69e2d7dcc5a08190b53691130d56cbc4 completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f293225a58819082bba82ad445864f completed April 29, 2026, 11:24 p.m.
PD Predicate disambiguation batch_69f287ad30048190b3ad3613486f277f completed April 29, 2026, 10:35 p.m.
PDg Predicate description generation batch_69f28b7ff1808190870dfe9af789a1eb completed April 29, 2026, 10:51 p.m.
Created at: April 18, 2026, 1:57 a.m.