Triple
T21550930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron of the Empire |
E531758
|
entity |
| Predicate | typicalRights |
P144196
|
FINISHED |
| Object | local jurisdiction over estates |
—
|
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: local jurisdiction over estates | Statement: [Baron of the Empire, typicalRights, local jurisdiction over estates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRights Context triple: [Baron of the Empire, typicalRights, local jurisdiction over estates]
-
A.
typicalRegionRights
Indicates that certain rights or permissions are characteristic or standard for a given region.
-
B.
characterizesRightsAs
Indicates that one entity describes, defines, or portrays the nature or status of another entity’s rights in a particular way.
-
C.
rightsInclude
Indicates that one set of rights encompasses, contains, or subsumes another set of rights.
-
D.
rightsStatementType
Indicates the specific category or nature of a rights statement that applies to a resource or entity.
-
E.
rightsRecognizedIn
Indicates that certain rights are formally acknowledged or upheld within a specified context, such as a legal system, jurisdiction, or document.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb59258b88190966c18f1f519dad6 |
completed | April 27, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:28 p.m.