Triple
T26153743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Reeves |
E659898
|
entity |
| Predicate | protectedRightsTo |
P13930
|
FINISHED |
| Object | Jim Reeves recordings |
—
|
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: Jim Reeves recordings | Statement: [Mary Reeves, protectedRightsTo, Jim Reeves recordings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectedRightsTo Context triple: [Mary Reeves, protectedRightsTo, Jim Reeves recordings]
-
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.
restrictedRight
Indicates that an entity’s ability to exercise a particular right is limited, constrained, or subject to specific conditions or prohibitions.
-
D.
rightsInclude
Indicates that one set of rights encompasses, contains, or subsumes another set of rights.
-
E.
protectedFor
Indicates that something is safeguarded or preserved specifically for the benefit, use, or rights of a particular entity or purpose.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 26, 2026, 8:26 p.m.