Triple
T26858908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suri dynasty |
E676271
|
entity |
| Predicate | interruptedRuleOf |
P59504
|
FINISHED |
| Object | Mughal Empire |
—
|
NE NERFINISHED |
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: Mughal Empire | Statement: [Suri dynasty, interruptedRuleOf, Mughal Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interruptedRuleOf Context triple: [Suri dynasty, interruptedRuleOf, Mughal Empire]
-
A.
endedContinuousRuleOf
Indicates that one entity brought an ongoing rule, regulation, or governing condition applied to another entity to an end.
-
B.
restartRule
Indicates the conditions or rules under which a process, task, or system is restarted after stopping or failing.
-
C.
wasInterruptedBy
chosen
Indicates that an ongoing event, action, or process was stopped or disrupted by another event, action, or agent.
-
D.
possibleInterruption
Indicates that one event, action, or process may interrupt, break into, or otherwise disrupt the continuity of another.
-
E.
disruptedIn
Indicates that a normal process, function, or state is interrupted, impaired, or thrown into disorder within the specified context.
- 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 27, 2026, 5:23 a.m.