Triple
T9476698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kemalism |
E228532
|
entity |
| Predicate | hasSecularReform |
P41349
|
FINISHED |
| Object | abolition of the Caliphate |
—
|
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: abolition of the Caliphate | Statement: [Kemalism, hasSecularReform, abolition of the Caliphate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecularReform Context triple: [Kemalism, hasSecularReform, abolition of the Caliphate]
-
A.
underwentReformation
chosen
Indicates that an entity experienced a significant process of change, restructuring, or reform that altered its previous state or practices.
-
B.
reformedOn
Indicates that an entity underwent a reform, change, or restructuring at a specific point in time or on a particular date.
-
C.
denominationReform
Indicates a change or restructuring in a religious denomination’s doctrines, practices, or organizational form.
-
D.
laterReformedAs
Indicates that an entity was subsequently reorganized, renamed, or transformed into another entity at a later time.
-
E.
functionAfterReformation
Indicates that one function or role exists or is performed in the state or period following a process of reformation or reform.
- 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_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd80127744819082176b2d4417216e |
completed | April 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:54 p.m.