Triple
T18624925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Bishops |
E455254
|
entity |
| Predicate | hasDecisionMakingRoleIn |
P8542
|
FINISHED |
| Object | church governance |
—
|
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: church governance | Statement: [House of Bishops, hasDecisionMakingRoleIn, church governance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDecisionMakingRoleIn Context triple: [House of Bishops, hasDecisionMakingRoleIn, church governance]
-
A.
hasDecisionMakingPower
Indicates that one entity possesses the authority or ability to make decisions that affect another entity or a given context.
-
B.
hasDecisionMaker
Indicates that one entity serves as the decision-making authority or agent for another entity.
-
C.
decisionRole
Indicates that an entity participates in a decision-making process with a specified role or function in that decision.
-
D.
decisionMakingRole
chosen
Indicates that an entity holds responsibility or authority in making decisions for or on behalf of another entity or group.
-
E.
makesDecisionBy
Indicates that one entity determines or chooses an outcome, course of action, or judgment by means of another entity, method, or process.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54f039b408190b51fe770a4c530ec |
completed | April 19, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.