Triple
T30212148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primate (ecclesiastical title) |
E768095
|
entity |
| Predicate | mayIncludePower |
P169370
|
FINISHED |
| Object | convene national synods |
—
|
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: convene national synods | Statement: [Primate (ecclesiastical title), mayIncludePower, convene national synods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayIncludePower Context triple: [Primate (ecclesiastical title), mayIncludePower, convene national synods]
-
A.
mayIncludeMode
Indicates that one entity is allowed to contain or support a particular mode as one of its possible configurations or options.
-
B.
mayIncludeFeature
Indicates that one entity is allowed or able to contain, incorporate, or be associated with a particular feature.
-
C.
mayIncludeRequirement
Indicates that something can optionally contain or encompass a particular requirement as part of its definition or structure.
-
D.
mayPresent
Indicates that one entity is permitted or authorized to present, display, or introduce another entity or item.
-
E.
mayAllowUse
Indicates that one entity has the potential or permission to allow another entity to use or access something.
- 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ff185488190a49b208e4ac6cf59 |
completed | May 2, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 7:33 p.m.