Triple
T27351430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Approval of the Clementine Vulgate |
E684369
|
entity |
| Predicate | approvedTextType |
P81489
|
FINISHED |
| Object | Latin Vulgate |
—
|
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: Latin Vulgate | Statement: [Approval of the Clementine Vulgate, approvedTextType, Latin Vulgate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approvedTextType Context triple: [Approval of the Clementine Vulgate, approvedTextType, Latin Vulgate]
-
A.
approvalType
Indicates the specific category or kind of approval that has been granted or requested in the relationship between entities.
-
B.
allowsText
Indicates that one entity permits or supports the use, input, or display of textual content in relation to another entity.
-
C.
approvedAs
Indicates that one entity has been officially accepted, authorized, or validated in a particular role, status, or capacity by another entity.
-
D.
approvalStatus
Indicates the current state of authorization or acceptance granted to an entity or action.
-
E.
documentTypeApproved
chosen
Indicates that a specific type or category of document has been formally reviewed and granted approval for use or processing.
- 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_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 27, 2026, 11:48 a.m.