Triple
T4678182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muscovite army |
E103732
|
entity |
| Predicate | significantReformPeriod |
P50931
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Muscovite army, significantReformPeriod, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantReformPeriod Context triple: [Muscovite army, significantReformPeriod, 16th century]
-
A.
timeOfMajorReforms
chosen
Indicates the specific time period during which significant reforms or major changes took place.
-
B.
notableReform
Indicates that an entity is recognized for having initiated, led, or been central to a significant reform or transformative change in a system, policy, or institution.
-
C.
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.
-
D.
survivedReformsOf
Indicates that one entity continued to exist or remain in its role despite reforms, changes, or restructuring initiated by another entity.
-
E.
goalOfReforms
Indicates that a reform or set of reforms is undertaken with the aim or intended objective of achieving a particular outcome.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6217e0088190836570522e324dc6 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.