Triple
T27351428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Approval of the Clementine Vulgate |
E684369
|
entity |
| Predicate | hasApprover |
P807
|
FINISHED |
| Object | Pope Clement VIII |
—
|
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: Pope Clement VIII | Statement: [Approval of the Clementine Vulgate, hasApprover, Pope Clement VIII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApprover Context triple: [Approval of the Clementine Vulgate, hasApprover, Pope Clement VIII]
-
A.
hasApprovalType
Indicates that an entity is associated with a specific category or kind of approval it has received or requires.
-
B.
hasApprovalAuthority
Indicates that an entity possesses the power or right to review and formally approve or reject decisions, actions, or requests made by others.
-
C.
approvedBy
chosen
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
D.
isApprovedFor
Indicates that one entity has been officially authorized, accepted, or permitted for use, access, or association with another entity.
-
E.
hasAppointer
Indicates that one entity is responsible for appointing or assigning another entity to a role, position, or function.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 27, 2026, 11:48 a.m.