Triple
T11194983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paschal III |
E264898
|
entity |
| Predicate | issuedAct |
P97785
|
FINISHED |
| Object | canonization of Charlemagne |
—
|
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: canonization of Charlemagne | Statement: [Paschal III, issuedAct, canonization of Charlemagne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuedAct Context triple: [Paschal III, issuedAct, canonization of Charlemagne]
-
A.
issuedWith
Indicates that one entity is formally provided, granted, or supplied together with another entity as part of the same issuance event.
-
B.
issuedDocument
Indicates that one entity has formally created and provided an official document to another entity.
-
C.
isIssued
Indicates that an authoritative source formally provides, distributes, or makes something (such as a document, order, or item) officially available to a recipient.
-
D.
authorizationAct
Indicates that an entity formally grants permission or legal authority for another entity to perform a specific action or set of actions.
-
E.
formedAct
Indicates that an entity initiated or created a particular action, event, or activity.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8bf14e481908563b15790af4d20 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:29 p.m.