Triple
T207161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savior |
E4633
|
entity |
| Predicate | coreToPractice |
P1188
|
FINISHED |
| Object | Christian worship |
—
|
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: Christian worship | Statement: [Savior, coreToPractice, Christian worship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreToPractice Context triple: [Savior, coreToPractice, Christian worship]
-
A.
currentBestPractice
Indicates that something represents the most up-to-date and widely accepted recommended method or standard at the present time.
-
B.
hasImportantPractice
chosen
Indicates that an entity engages in or possesses a practice, activity, or procedure considered significant or essential within a given context.
-
C.
practice
Indicates that an entity regularly performs an activity or skill, typically to improve proficiency or maintain competence.
-
D.
coreIdea
Indicates the central concept or primary message that underlies or unifies something, such as a text, argument, or work.
-
E.
appliesTheory
Indicates that an entity uses or implements a particular theory in analyzing, explaining, or addressing something.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b4c7f908190876c1041db52dffc |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.