Triple
T34646164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De donis conditionalibus |
E889699
|
entity |
| Predicate | protectedRightsOf |
P13930
|
FINISHED |
| Object | heirs of the body |
—
|
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: heirs of the body | Statement: [De donis conditionalibus, protectedRightsOf, heirs of the body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectedRightsOf Context triple: [De donis conditionalibus, protectedRightsOf, heirs of the body]
-
A.
rightsEnforced
Indicates that legal or moral rights are actively upheld, protected, or compelled through appropriate mechanisms or actions.
-
B.
protectsRight
chosen
Indicates that one entity safeguards, upholds, or defends the legal or moral rights of another entity.
-
C.
rightsInclude
Indicates that one set of rights encompasses, contains, or subsumes another set of rights.
-
D.
restrictedRight
Indicates that an entity’s ability to exercise a particular right is limited, constrained, or subject to specific conditions or prohibitions.
-
E.
typicalRights
Indicates that one entity normally or customarily has certain rights or entitlements in relation to another 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f73397e5488190a9cdce98a0ac0383 |
completed | May 3, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69f732f3ad248190b4bcbf589d000f0d |
completed | May 3, 2026, 11:35 a.m. |
Created at: May 1, 2026, 2:04 a.m.