Triple
T36706183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apostolic Constitution |
E906365
|
entity |
| Predicate | mayReform |
P132014
|
FINISHED |
| Object | Roman Curia |
—
|
NE NERFINISHED |
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: Roman Curia | Statement: [Apostolic Constitution, mayReform, Roman Curia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayReform Context triple: [Apostolic Constitution, mayReform, Roman Curia]
-
A.
canReform
chosen
Indicates that an entity has the ability or potential to change, improve, or be corrected from a previous state, behavior, or condition.
-
B.
mayForm
Indicates that one entity has the potential or permission to be combined or configured to create, constitute, or result in another entity or structure.
-
C.
subjectToReformBy
Indicates that an entity is undergoing or designated for changes, improvements, or restructuring carried out by another entity.
-
D.
reform
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
-
E.
mayAmend
Indicates that one party has the authority or permission to modify, revise, or change something that already exists.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c80f84248190a9b3276c180191d2 |
completed | May 3, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.