Triple
T3757324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dei Providentis |
E82078
|
entity |
| Predicate | authoritativeStatus |
P3927
|
FINISHED |
| Object | binding for the Roman Curia |
—
|
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: binding for the Roman Curia | Statement: [Dei Providentis, authoritativeStatus, binding for the Roman Curia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authoritativeStatus Context triple: [Dei Providentis, authoritativeStatus, binding for the Roman Curia]
-
A.
authoritativeFor
Indicates that one entity has recognized control, responsibility, or decision-making power over another entity or domain.
-
B.
canonicalStatus
chosen
Indicates the formal or official standing of an entity within an established authoritative or normative system.
-
C.
authorshipStatus
Indicates the current state or condition of an entity’s role as an author in relation to a work (e.g., confirmed, disputed, anonymous, or pending).
-
D.
associatedStatus
Indicates that one entity is linked to or characterized by a particular status or condition.
-
E.
canonicalStatusIn
Indicates that something has a particular canonical or officially recognized status within a specified context or system.
- 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_69ad8b1db40081908b61ffa6b78afd4d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcbbe7a6081909b0f835a77941300 |
completed | March 8, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69adc04c851c8190ae5eaebf36df539b |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.