Triple
T19247520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of England in the Colony of Virginia |
E481301
|
entity |
| Predicate | hasPriesthoodType |
P3092
|
FINISHED |
| Object | ordained clergy |
—
|
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: ordained clergy | Statement: [Church of England in the Colony of Virginia, hasPriesthoodType, ordained clergy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPriesthoodType Context triple: [Church of England in the Colony of Virginia, hasPriesthoodType, ordained clergy]
-
A.
hadPriesthood
Indicates that an entity possessed or held a recognized priestly office or religious authority.
-
B.
hasClergyType
chosen
Indicates the specific category or role of clergy associated with an entity.
-
C.
hasViewOnPriesthood
Indicates that an entity holds a particular stance, opinion, or doctrinal position regarding the concept, role, or practice of priesthood.
-
D.
hasMarriedPriesthoodTradition
Indicates that a religious group or denomination maintains a tradition in which members of its priesthood are permitted or expected to be married.
-
E.
hasHolinessType
Indicates a relationship where an entity is assigned or associated with a specific type or category of holiness.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb2e7cf881908dafd45d7a305c52 |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:27 p.m.