Triple
T11112097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rashtrakuta court |
E262780
|
entity |
| Predicate | courtOfficials |
P16689
|
FINISHED |
| Object | ministers |
—
|
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: ministers | Statement: [Rashtrakuta court, courtOfficials, ministers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtOfficials Context triple: [Rashtrakuta court, courtOfficials, ministers]
-
A.
courtOfficial
chosen
Indicates that an entity serves in an official capacity within a court, holding an authorized role in judicial or legal proceedings.
-
B.
numberOfOfficials
Indicates the total count of officials associated with a given entity or context.
-
C.
umpires
Indicates that an entity serves as the umpire overseeing, judging, or officiating an event, activity, or interaction involving another entity.
-
D.
courtRole
Indicates the specific capacity or position an entity holds within a court proceeding or judicial context.
-
E.
courtRank
Indicates the formal hierarchical rank or status an individual holds within a court or courtly system.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79aa42ec4819085a2e802e00d9f02 |
completed | April 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.