Triple
T12865598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglican bishops |
E307710
|
entity |
| Predicate | lead |
P4351
|
FINISHED |
| Object | diocesan 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: diocesan synods | Statement: [Anglican bishops, lead, diocesan synods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lead Context triple: [Anglican bishops, lead, diocesan synods]
-
A.
leadSingle
Indicates that an entity serves as the primary or featured performer, contributor, or focus in a single work or instance.
-
B.
leads
Indicates having primary responsibility for directing, guiding, or managing another entity or group toward a goal or outcome.
-
C.
leadingOrgan
chosen
Indicates that one entity serves as the primary or most responsible organizing body or authority for another entity or activity.
-
D.
leadsInto
Indicates that one entity serves as an entry or transition point that directly connects or opens into another entity.
-
E.
leadShip
Indicates that one entity serves as the commander or person in charge of a ship belonging to or associated 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_69d7bdf69bc48190af6c2621f28ca351 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa3002881908000357b1f95a3ac |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:37 p.m.