Triple
T34959448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Man Singh I of Amber |
E1008211
|
entity |
| Predicate | rankInAkbarsNobility |
P66828
|
FINISHED |
| Object | one of the highest-ranking nobles |
—
|
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: one of the highest-ranking nobles | Statement: [Man Singh I of Amber, rankInAkbarsNobility, one of the highest-ranking nobles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankInAkbarsNobility Context triple: [Man Singh I of Amber, rankInAkbarsNobility, one of the highest-ranking nobles]
-
A.
nobleRankIn
chosen
Indicates that an entity holds a specified noble rank within a particular political or territorial jurisdiction.
-
B.
nobleRankOf
Indicates that one entity holds a specific noble title or rank within a hierarchical nobility system.
-
C.
nobleRankInOrder
Indicates that an entity holds a specific noble rank at a particular position within an established order of nobility.
-
D.
rankRelativeToSheikh
Indicates the comparative rank or status of an entity in relation to a sheikh.
-
E.
nobleRankInHierarchy
Indicates the relative position or level of a noble title within a structured hierarchy of ranks.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4 p.m.