Triple

T34111208
Position Surface form Disambiguated ID Type / Status
Subject Mughal period E874842 entity
Predicate hasAdministrativeSystem P180617 FINISHED
Object mansabdari system 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: mansabdari system | Statement: [Mughal period, hasAdministrativeSystem, mansabdari system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAdministrativeSystem
Context triple: [Mughal period, hasAdministrativeSystem, mansabdari system]
  • A. operatesInAdministrativeSystem
    Indicates that an entity functions or carries out its activities within a specified administrative or bureaucratic system.
  • B. hasAdministrativeType
    Indicates that an entity is associated with a specific category or level of administrative classification (such as type of jurisdiction or administrative unit).
  • C. usedAdministrativeSystemOf
    Indicates that one entity made use of another entity’s administrative system to perform or manage its administrative functions.
  • D. hasAdministrationModel chosen
    Indicates that an entity is associated with or governed by a particular administration or management model.
  • E. hasAdministrationMethod
    Indicates the method or route by which something (typically a drug, treatment, or resource) is administered or delivered.
  • 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_69f349a80d4481908527317d43f5c579 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69fd7e364a648190a1e9e1d9fc76e99e completed May 8, 2026, 6:09 a.m.
PD Predicate disambiguation batch_69fd7bb547608190a3b04dddbca6b8bc completed May 8, 2026, 5:59 a.m.
Created at: May 1, 2026, 1:53 a.m.