Triple
T30448572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mekteb-i Mülkiye |
E774646
|
entity |
| Predicate | associatedWithReformEra |
P136696
|
FINISHED |
| Object | Tanzimat |
E18681
|
NE 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: Tanzimat | Statement: [Mekteb-i Mülkiye, associatedWithReformEra, Tanzimat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithReformEra Context triple: [Mekteb-i Mülkiye, associatedWithReformEra, Tanzimat]
-
A.
reformEraChange
Indicates a change or transition that occurs during a period of reform or as part of a reform era.
-
B.
associatedReform
chosen
Indicates a relationship where one entity is linked to, connected with, or involved in a particular reform or set of reforms.
-
C.
associatedReforms
Indicates a relationship where certain reforms are linked or connected to a given entity, such as a policy, event, or individual.
-
D.
associatedWithReformMovement
Indicates that an entity is connected or linked in some way to a reform movement, such as by participation, support, influence, or affiliation.
-
E.
regionAfterReform
Indicates that one region is the successor or resulting region of another after an administrative or political reform.
- F. None of above.
Provenance (4 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2798c765808190a0695d73586cf854 |
completed | June 9, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:09 p.m.