Triple
T6254069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocesan Synod of Coventry |
E140116
|
entity |
| Predicate | canDebate |
P69738
|
FINISHED |
| Object | national and diocesan church issues |
—
|
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: national and diocesan church issues | Statement: [Diocesan Synod of Coventry, canDebate, national and diocesan church issues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canDebate Context triple: [Diocesan Synod of Coventry, canDebate, national and diocesan church issues]
-
A.
canSpeakInDebates
Indicates that an entity has the ability or permission to speak during formal debates.
-
B.
hasDebate
Indicates that there is a formal discussion or argument between entities, typically presenting opposing viewpoints on a topic.
-
C.
fieldOfDebate
Indicates that something is the subject or domain around which a debate or argumentative discussion is centered.
-
D.
mainDebateTopic
Indicates that a specified subject or issue is the primary focus or central topic of a particular debate or discussion.
-
E.
debateTopic
Indicates that one entity serves as the subject or issue being discussed or argued about in a debate involving another entity.
- F. None of above. chosen
Provenance (4 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063625608819081f5422112c80ce5 |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c05707d5408190a1d0fd80414ad957 |
completed | March 22, 2026, 8:54 p.m. |
Created at: March 22, 2026, 4:24 p.m.