Triple
T20049141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emancipation Manifesto |
E499145
|
entity |
| Predicate | legalStatusOfSerfsAfter |
P100585
|
FINISHED |
| Object | personally free peasants |
—
|
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: personally free peasants | Statement: [Emancipation Manifesto, legalStatusOfSerfsAfter, personally free peasants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusOfSerfsAfter Context triple: [Emancipation Manifesto, legalStatusOfSerfsAfter, personally free peasants]
-
A.
laterFeudalStatus
Indicates that one entity held a particular feudal status or rank at a later time than another entity or than an earlier status.
-
B.
legalStatusOfSlavery
Indicates the legal condition or permissibility of slavery within a given jurisdiction, time, or context.
-
C.
feudalStatus
Indicates the hierarchical social or legal position an entity holds within a feudal system, such as lord, vassal, or serf.
-
D.
legalStatusAfter1792
Indicates the legal status or condition that an entity held after the year 1792.
-
E.
legalStatus19thCentury
chosen
Indicates the legal classification or condition that an entity held during the 19th century.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6632cccb481908278c8b2930a8c26 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:37 p.m.