Triple
T9025187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minister of Word and Sacrament |
E216028
|
entity |
| Predicate | mayServeIn |
P23319
|
FINISHED |
| Object | local congregation |
—
|
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: local congregation | Statement: [Minister of Word and Sacrament, mayServeIn, local congregation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayServeIn Context triple: [Minister of Word and Sacrament, mayServeIn, local congregation]
-
A.
mayServeOn
Indicates that one entity is permitted or eligible to serve on another entity, such as a group, body, or committee.
-
B.
canServeIn
chosen
Indicates that one entity is eligible, authorized, or suitable to perform a role, function, or duty within another entity, context, or organization.
-
C.
mayServe
Indicates that one entity is permitted or authorized to provide a service or function to another entity.
-
D.
alsoServeIn
Indicates that an entity serves in an additional role, position, or capacity alongside its primary one.
-
E.
canServeOn
Indicates that one entity is eligible or permitted to serve on another entity, such as a group, body, or committee.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7b902c81909fcbdc433a1acf7a |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.