Triple
T960682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reformed churches |
E20728
|
entity |
| Predicate | stressesPractice |
P12146
|
FINISHED |
| Object | expository preaching |
—
|
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: expository preaching | Statement: [Reformed churches, stressesPractice, expository preaching]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stressesPractice Context triple: [Reformed churches, stressesPractice, expository preaching]
-
A.
homePractice
Indicates that an activity, skill, or task is being practiced or carried out in a home setting rather than in a formal or external environment.
-
B.
practice
Indicates that an entity regularly performs an activity or skill, typically to improve proficiency or maintain competence.
-
C.
typicalPractice
chosen
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
-
D.
practiceType
Indicates the specific kind or category of practice associated with an entity or activity.
-
E.
stillPracticedIn
Indicates that a tradition, custom, or practice continues to be actively carried out or observed in a specified place or context.
- 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b4144c208190980936347a95e233 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a2e23c8190b932fe88b02f995d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.