Triple
T2287780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vicar of Christ |
E51432
|
entity |
| Predicate | impliesResponsibilityFor |
P636
|
FINISHED |
| Object | unity of the Church |
—
|
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: unity of the Church | Statement: [Vicar of Christ, impliesResponsibilityFor, unity of the Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliesResponsibilityFor Context triple: [Vicar of Christ, impliesResponsibilityFor, unity of the Church]
-
A.
responsibleFor
chosen
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
-
B.
accountableThrough
Indicates that one entity bears responsibility or can be held answerable by means of, or via the mechanism provided by, another entity or process.
-
C.
implies
Indicates that the truth of one statement guarantees or leads logically to the truth of another statement.
-
D.
establishesLiabilityFor
Indicates that one party is held legally responsible or accountable for a particular act, omission, or outcome.
-
E.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
- 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc24868048190940512fd6449d99e |
completed | March 7, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69abbdbb9e4c819085fc588626ec7c09 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.