Triple
T4341392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cum inter multiplices |
E97787
|
entity |
| Predicate | documentClass |
P12715
|
FINISHED |
| Object | pontifical bull |
—
|
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: pontifical bull | Statement: [Cum inter multiplices, documentClass, pontifical bull]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentClass Context triple: [Cum inter multiplices, documentClass, pontifical bull]
-
A.
documentationType
Indicates the specific category or kind of documentation associated with or required for an entity or process.
-
B.
documentModel
chosen
Indicates that an entity serves as or is associated with a specific structured representation or schema of a document.
-
C.
doctypeSyntax
Indicates that one entity specifies or conforms to the syntax rules of a document type declaration (DOCTYPE) used in markup languages.
-
D.
documentNumber
Indicates the unique identifying number assigned to a specific document in the relationship.
-
E.
documentSource
Indicates that one entity serves as the origin, provider, or provenance source for a given document.
- 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35170a6648190a15ffb21640ee478 |
completed | March 12, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:14 p.m.