Triple
T32404069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsarist government |
E828028
|
entity |
| Predicate | legalStatusOfSerfdom |
P6136
|
FINISHED |
| Object | serfdom legally recognized until 1861 |
—
|
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: serfdom legally recognized until 1861 | Statement: [Tsarist government, legalStatusOfSerfdom, serfdom legally recognized until 1861]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusOfSerfdom Context triple: [Tsarist government, legalStatusOfSerfdom, serfdom legally recognized until 1861]
-
A.
legalStatusOfSlavery
chosen
Indicates the legal condition or permissibility of slavery within a given jurisdiction, time, or context.
-
B.
usesSlavery
Indicates that an entity employs or relies on enslaved people or forced labor as part of its operations or activities.
-
C.
historicalPeriodOfEnslavement
Indicates the specific historical period during which an entity was subjected to enslavement.
-
D.
wasEnslavedIn
Indicates that an entity was held in a state of slavery within a specified place or context.
-
E.
numberOfEnslaved
Indicates the quantity of individuals who were held in a state of enslavement in relation to a given entity or context.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
Created at: May 1, 2026, 12:53 a.m.