Triple
T30084731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A New Commandment |
E764571
|
entity |
| Predicate | intendedContext |
P81164
|
FINISHED |
| Object | church service |
—
|
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: church service | Statement: [A New Commandment, intendedContext, church service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedContext Context triple: [A New Commandment, intendedContext, church service]
-
A.
intendedTargetContext
chosen
Indicates the context, situation, or setting that an action, message, or object is specifically designed or meant to be used in or directed toward.
-
B.
contextOf
Indicates that one entity provides the situational, informational, or environmental background within which another entity exists, occurs, or is interpreted.
-
C.
contextSensitive
Indicates that the relationship or behavior depends on the surrounding context or situation rather than being fixed or absolute.
-
D.
context
Indicates that one entity provides the surrounding circumstances, setting, or background within which another entity, event, or statement occurs or is interpreted.
-
E.
intendedWith
Indicates that one entity is the planned or desired target, recipient, or context for the use or application of another entity.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 29, 2026, 7:03 p.m.