Triple
T2638606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Milwaukee |
E62807
|
entity |
| Predicate | usesGovernanceModel |
P2995
|
FINISHED |
| Object | Episcopal polity |
—
|
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: Episcopal polity | Statement: [Diocese of Milwaukee, usesGovernanceModel, Episcopal polity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGovernanceModel Context triple: [Diocese of Milwaukee, usesGovernanceModel, Episcopal polity]
-
A.
governanceModel
chosen
Indicates the type or structure of authority, decision-making, and control that defines how an entity is directed and overseen.
-
B.
usesPolicyModel
Indicates that one entity applies, relies on, or operates according to a particular policy model.
-
C.
governanceActor
Indicates that an entity plays a role in governing, managing, or overseeing another entity, process, or domain.
-
D.
isRuleGoverned
Indicates that an entity’s behavior, structure, or operation is determined and constrained by explicit rules or formal regulations.
-
E.
governance
Indicates the relationship in which one entity exercises authority, control, or decision-making power over the policies, actions, or direction of another entity or system.
- 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_69ab4c3f2dcc819082df80f5e032f690 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abd8e470ac8190bd0d6de6805afcd0 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd812849881908f956845a80e0205 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.