Triple
T28716648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ordinary General Assembly of the Synod of Bishops |
E729977
|
entity |
| Predicate | finalDecisionsMadeBy |
P73913
|
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: [Ordinary General Assembly of the Synod of Bishops, finalDecisionsMadeBy, Pope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalDecisionsMadeBy Context triple: [Ordinary General Assembly of the Synod of Bishops, finalDecisionsMadeBy, Pope]
-
A.
decisionsTakenBy
chosen
Indicates that one or more decisions are made or taken by a specified agent or entity.
-
B.
decisionResultsIn
Indicates that a particular decision leads to, causes, or brings about a specific outcome or result.
-
C.
decisionsAre
Indicates that certain choices, judgments, or resolutions possess a specified quality, status, or classification.
-
D.
hasFinalDecisionOn
Indicates that one entity holds the ultimate authority or responsibility to make and enforce a conclusive decision regarding another entity or matter.
-
E.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 28, 2026, 5:51 a.m.