Triple
T31993404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qajar Persian Army |
E816928
|
entity |
| Predicate | laterReformElement |
P116824
|
FINISHED |
| Object | European-drilled infantry |
—
|
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: European-drilled infantry | Statement: [Qajar Persian Army, laterReformElement, European-drilled infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterReformElement Context triple: [Qajar Persian Army, laterReformElement, European-drilled infantry]
-
A.
lastReform
Indicates the most recent reform or change that was applied to an entity, typically linking the entity to its latest reform event or version.
-
B.
replacedInReform
Indicates that one entity was substituted or superseded by another as part of a formal reform or restructuring process.
-
C.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
D.
scriptAfterReform
Indicates that one script or writing system is used after a reform or modification has been applied to another script.
-
E.
laterForms
chosen
Indicates that one entity is a subsequent or more recent form, version, or stage of another entity in a temporal or developmental sequence.
- 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_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
Created at: May 1, 2026, 12:13 a.m.