Triple
T5629417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mughal culture |
E147795
|
entity |
| Predicate | hasCourtPractice |
P64670
|
FINISHED |
| Object | patronage of scholars |
—
|
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: patronage of scholars | Statement: [Mughal culture, hasCourtPractice, patronage of scholars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCourtPractice Context triple: [Mughal culture, hasCourtPractice, patronage of scholars]
-
A.
hasCourts
Indicates that an entity possesses, contains, or is equipped with one or more courts (e.g., legal, sports, or judicial facilities).
-
B.
hasCourtInEach
Indicates that an entity possesses or maintains a court in every member of a specified set of locations or jurisdictions.
-
C.
hasCourtPrecedence
Indicates that one court decision or ruling holds authoritative priority over another in legal reasoning or application.
-
D.
hasTribunal
Indicates that an entity is associated with or subject to a specific tribunal, such as a court or adjudicative body, that has authority over its cases or matters.
-
E.
hasStateCourt
Indicates that a given jurisdiction or region possesses an official court that operates at the state level.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0223b1e54819099fe5fc84ed17a88 |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:40 p.m.