Triple
T26689424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concordat of Bologna |
E672834
|
entity |
| Predicate | confirmedAuthorityOf |
P92261
|
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: [Concordat of Bologna, confirmedAuthorityOf, Pope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confirmedAuthorityOf Context triple: [Concordat of Bologna, confirmedAuthorityOf, Pope]
-
A.
authorityAffirmedBy
chosen
Indicates that the legitimacy or validity of an authority is confirmed, endorsed, or supported by another party or source.
-
B.
confirmedBy
Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
-
C.
confirmedAs
Indicates that one entity has been officially verified, recognized, or validated as being identical to or serving in the role of another entity.
-
D.
usesAuthorityOf
Indicates that one entity exercises power, rights, or influence derived from or on behalf of another entity’s authority.
-
E.
jointAuthorityOf
Indicates that two or more entities share formal power or control over a decision, resource, or domain.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 3:25 a.m.