Triple
T6517746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mughal legal system |
E148306
|
entity |
| Predicate | hadCourtLevel |
P71353
|
FINISHED |
| Object | imperial court |
—
|
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: imperial court | Statement: [Mughal legal system, hadCourtLevel, imperial court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadCourtLevel Context triple: [Mughal legal system, hadCourtLevel, imperial court]
-
A.
hasLowerCourt
Indicates that one court functions as a subordinate or inferior court within the judicial hierarchy of another court.
-
B.
highestTrialCourtOf
Indicates that one entity serves as the supreme or final-level trial court within the judicial hierarchy of another entity (such as a jurisdiction or legal system).
-
C.
hasSeniorCourt
Indicates that one court is hierarchically subordinate to another court that serves as its senior or higher-level authority.
-
D.
higherCourtOf
Indicates that one court has legal authority to review, overrule, or supervise the decisions and actions of another, lower court in the judicial hierarchy.
-
E.
hasCourtDivision
Indicates that a court is organized into, or belongs to, a specific internal division or section within the judicial system.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac108abc819082d1368af6611a92 |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:44 p.m.