Triple
T414296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mennonites |
E9557
|
entity |
| Predicate | governanceForm |
P2995
|
FINISHED |
| Object | congregational 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: congregational polity | Statement: [Mennonites, governanceForm, congregational polity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governanceForm Context triple: [Mennonites, governanceForm, congregational polity]
-
A.
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.
-
B.
governmentFormCreated
Indicates that one entity established or instituted a particular form or system of government for another entity.
-
C.
governanceChange
Indicates a change in the structure, rules, or authority of how an entity, organization, or system is governed.
-
D.
governanceModel
chosen
Indicates the type or structure of authority, decision-making, and control that defines how an entity is directed and overseen.
-
E.
governs
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edcff4688190809d83d112ff25a5 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.