Triple
T6444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Episcopal Church |
E129
|
entity |
| Predicate | polity |
P220
|
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: [Episcopal Church, polity, episcopal polity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: polity Context triple: [Episcopal Church, polity, episcopal polity]
-
A.
politicalParty
Indicates that an entity is affiliated with, belongs to, or is a member of a specific political party.
-
B.
governmentType
chosen
Indicates the form or system of governance under which an entity (such as a country or organization) is organized and ruled.
-
C.
ideology
Indicates the belief system or set of political, social, or philosophical principles that an entity adheres to or promotes.
-
D.
election
Indicates a relationship where individuals or groups formally choose someone or something from among candidates or options, typically through a voting process.
-
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_69a23bb612708190b09f25385e4b63d1 |
completed | Feb. 28, 2026, 12:49 a.m. |
| NER | Named-entity recognition | batch_69a2421836f08190b54fc40edeb1a96b |
completed | Feb. 28, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69a23fe064c881909496fd0e6b0e18d7 |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 12:54 a.m.