Triple
T19074802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millenary Petition |
E466876
|
entity |
| Predicate | requestedReform |
P134219
|
FINISHED |
| Object | stricter observance of the Sabbath |
—
|
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: stricter observance of the Sabbath | Statement: [Millenary Petition, requestedReform, stricter observance of the Sabbath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requestedReform Context triple: [Millenary Petition, requestedReform, stricter observance of the Sabbath]
-
A.
canReform
Indicates that an entity has the ability or potential to change, improve, or be corrected from a previous state, behavior, or condition.
-
B.
reform
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
-
C.
subjectToReformBy
Indicates that an entity is undergoing or designated for changes, improvements, or restructuring carried out by another entity.
-
D.
reformsBy
Indicates that one entity initiates, implements, or is responsible for changes or improvements (reforms) affecting another entity.
-
E.
requestedRevisionsBy
Indicates that one entity has asked another entity to make changes or revisions to something.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e3c7b08190bf6448ead11ba916 |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.