Triple
T4176931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Shahryar |
E86498
|
entity |
| Predicate | undergoesChange |
P6390
|
FINISHED |
| Object | moral transformation |
—
|
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: moral transformation | Statement: [King Shahryar, undergoesChange, moral transformation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undergoesChange Context triple: [King Shahryar, undergoesChange, moral transformation]
-
A.
undergoing
Indicates that an entity is currently experiencing, being subjected to, or in the process of a particular action, change, or treatment.
-
B.
changesEvery
Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
-
C.
underwent
chosen
Indicates that an entity experienced or was subjected to a process, event, or change, typically as the patient of an action.
-
D.
typicalColorChange
Indicates a characteristic or commonly observed change in color that an entity undergoes under normal or expected conditions.
-
E.
reasonForChange
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.