Triple
T26585902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leibeigenschaftspatent |
E667208
|
entity |
| Predicate | affectedClass |
P167292
|
FINISHED |
| Object | serfs |
—
|
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: serfs | Statement: [Leibeigenschaftspatent, affectedClass, serfs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedClass Context triple: [Leibeigenschaftspatent, affectedClass, serfs]
-
A.
affectedEntity
Indicates that an entity is the one that is impacted, influenced, or acted upon as a result of an event, action, or process.
-
B.
affectedFunction
Indicates that one entity has an impact on, alters, or impairs the operation or behavior of another entity’s function.
-
C.
affectedProject
Indicates that one entity has an impact on, or is influenced by, a particular project.
-
D.
affectedProvision
Indicates that a particular legal provision is impacted, modified, or influenced by another action, decision, or provision.
-
E.
affectedRecord
Indicates that one entity is a record that is impacted, modified, or otherwise influenced as a result of an action or event involving another entity.
- F. None of above. chosen
Provenance (4 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 27, 2026, 2:05 a.m.