Triple
T14506996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2023 Synod on Synodality |
E340288
|
entity |
| Predicate | preparationPhase |
P2534
|
FINISHED |
| Object | diocesan consultations |
—
|
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: diocesan consultations | Statement: [2023 Synod on Synodality, preparationPhase, diocesan consultations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preparationPhase Context triple: [2023 Synod on Synodality, preparationPhase, diocesan consultations]
-
A.
preparationBegan
Indicates that the initial actions or processes required for something to be carried out or occur have started.
-
B.
preparationPeriod
Indicates the time span allocated before an event or action during which necessary preparations are made.
-
C.
preparationBy
Indicates that one entity is created, assembled, or made ready through the actions or processes performed by another entity.
-
D.
preparesFor
chosen
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
-
E.
preparedFor
Indicates that one entity has been made ready, equipped, or arranged in anticipation of use by or in connection with 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de94e40e44819084f323f8f9982b75 |
completed | April 14, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.