Triple
T555383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Methodist churches |
E11930
|
entity |
| Predicate | hasLayLeadership |
P3093
|
FINISHED |
| Object | lay preachers |
—
|
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: lay preachers | Statement: [Methodist churches, hasLayLeadership, lay preachers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLayLeadership Context triple: [Methodist churches, hasLayLeadership, lay preachers]
-
A.
hasLayMinistry
chosen
Indicates that an entity participates in or is associated with a lay (non-ordained) ministry role or service within a religious context.
-
B.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
C.
hasLayMembersCount
Indicates the number of lay (non-clergy or non-professional) members associated with an entity.
-
D.
leadershipPosition
Indicates that one entity holds a role of authority, guidance, or decision-making responsibility over others within an organization, group, or context.
-
E.
leaderSince
Indicates that an entity has held a leadership role over another entity starting from a specified point in time.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4991dd7008190a6c1bc8bc832456d |
completed | March 1, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69a494bc1f8c8190904356f3a8e801de |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.