Triple
T30896706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultan Husayn |
E787039
|
entity |
| Predicate | notableInternalIssue |
—
|
GENERATED |
| Object | court corruption |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableInternalIssue Context triple: [Sultan Husayn, notableInternalIssue, court corruption]
-
A.
hasInternalIssue
Indicates that an entity is experiencing a problem, fault, or malfunction originating within itself or its internal components or processes.
-
B.
hasNotableIssue
Indicates that an entity is associated with a significant problem, concern, or defect that is noteworthy or exceptional compared to typical cases.
-
C.
notableEarlyIssue
Indicates that the subject is a significant or noteworthy early edition, release, or version of the object.
-
D.
knownIssue
Indicates that the subject has an issue or problem that is already identified, recognized, or documented.
-
E.
notableInternalConflict
chosen
Indicates a significant or historically important internal conflict occurring within an entity, such as a country, organization, or group.
- F. None of above.
Provenance (1 batch)
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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:49 p.m.