Triple
T15100227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unigenitus (1343 bull) |
E360643
|
entity |
| Predicate | hasPapalSeal |
P94983
|
FINISHED |
| Object | bulla |
—
|
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: bulla | Statement: [Unigenitus (1343 bull), hasPapalSeal, bulla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPapalSeal Context triple: [Unigenitus (1343 bull), hasPapalSeal, bulla]
-
A.
hasEpiscopalSeal
Indicates that an entity possesses or is associated with a specific episcopal (bishop’s) seal.
-
B.
isSealOf
chosen
Indicates that one entity serves as the official seal, emblem, or stamp that authenticates, endorses, or formally represents another entity.
-
C.
usedSeal
Indicates that an entity has applied or employed a seal (e.g., for closure, authentication, or protection) on another entity.
-
D.
hasImprimatur
Indicates that an entity has received official approval or authorization, typically from a recognized authority.
-
E.
usesSealImage
Indicates that one entity employs or incorporates the seal image of another entity in some context or medium.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00550007481909e02ee1d597a4d37 |
completed | April 15, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:04 a.m.