Triple
T28244716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishop of Lübeck |
E712131
|
entity |
| Predicate | requiredConfirmationBy |
P85756
|
FINISHED |
| Object | Pope |
—
|
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 | Statement: [Prince-Bishop of Lübeck, requiredConfirmationBy, Pope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredConfirmationBy Context triple: [Prince-Bishop of Lübeck, requiredConfirmationBy, Pope]
-
A.
confirmationRequirement
chosen
Indicates that an action, decision, or change is contingent on receiving explicit confirmation from a specified party or process.
-
B.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
C.
ordinationRequiredFor
Indicates that a formal ordination is a necessary prerequisite for performing or holding the specified role, function, or office.
-
D.
confirmedBy
Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
-
E.
requiresProofOf
Indicates that one entity must provide formal evidence or documentation to validate or authorize another entity.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 27, 2026, 11 p.m.