Triple
T31993409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qajar Persian Army |
E816928
|
entity |
| Predicate | reformProgram |
P48027
|
FINISHED |
| Object | Abbas Mirza military reforms |
—
|
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: Abbas Mirza military reforms | Statement: [Qajar Persian Army, reformProgram, Abbas Mirza military reforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reformProgram Context triple: [Qajar Persian Army, reformProgram, Abbas Mirza military reforms]
-
A.
reform
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
-
B.
reformsBy
Indicates that one entity initiates, implements, or is responsible for changes or improvements (reforms) affecting another entity.
-
C.
typeOfReforms
Indicates the specific kinds or categories of reforms associated with an entity or situation.
-
D.
subjectToReformBy
chosen
Indicates that an entity is undergoing or designated for changes, improvements, or restructuring carried out by another entity.
-
E.
canReform
Indicates that an entity has the ability or potential to change, improve, or be corrected from a previous state, behavior, or condition.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:13 a.m.