Triple
T531580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mansabdari system |
E12233
|
entity |
| Predicate | rankRange |
P16498
|
FINISHED |
| Object | 10 to 5000 in Akbar’s time |
—
|
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: 10 to 5000 in Akbar’s time | Statement: [mansabdari system, rankRange, 10 to 5000 in Akbar’s time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankRange Context triple: [mansabdari system, rankRange, 10 to 5000 in Akbar’s time]
-
A.
rankFlagFor
Indicates that something is assigned or associated with a specific ranking flag used to mark its status or priority.
-
B.
depthRank
Indicates the relative ordering of entities based on how deep or distant they are along a specified depth dimension or hierarchy.
-
C.
rankingMember
Indicates that one entity is the highest-ranking or most senior member within a particular group, committee, or organization relative to the others.
-
D.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
E.
typicallyHoldsRank
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b257108190a537dffbb9d621b5 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49857e1148190aa782b82675cf0b5 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.