Triple
T16291258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sobornoye Ulozheniye |
E395526
|
entity |
| Predicate | effectOnRunawaySerfs |
P100102
|
FINISHED |
| Object | made search for runaway peasants indefinite |
—
|
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: made search for runaway peasants indefinite | Statement: [Sobornoye Ulozheniye, effectOnRunawaySerfs, made search for runaway peasants indefinite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnRunawaySerfs Context triple: [Sobornoye Ulozheniye, effectOnRunawaySerfs, made search for runaway peasants indefinite]
-
A.
effectOnPeasants
chosen
Indicates how an action, event, or condition impacts or influences peasants.
-
B.
numberOfSerfsFreed
Indicates the quantity of serfs that were liberated from serfdom in a given context or event.
-
C.
effectOnSlavery
Indicates the impact or influence that something has on the existence, extent, or conditions of slavery.
-
D.
hasEnslavedCharacter
Indicates that one entity has held another entity in a state of slavery or forced servitude.
-
E.
effectOnCossacks
Indicates the impact or consequences that something has on Cossacks as a group.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2491821d0819086cffdd7551ba85a |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.