Triple
T8330800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law of Christ |
E195067
|
entity |
| Predicate | normativeFunction |
P12028
|
FINISHED |
| Object | moral norm for Christian life |
—
|
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: moral norm for Christian life | Statement: [Law of Christ, normativeFunction, moral norm for Christian life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: normativeFunction Context triple: [Law of Christ, normativeFunction, moral norm for Christian life]
-
A.
normativeFor
chosen
Indicates that something establishes, prescribes, or encodes the norms, standards, or rules that should govern another thing’s behavior or state.
-
B.
normativeGoal
Indicates that one entity is a desired or prescribed objective, standard, or end state that another entity ought to pursue or realize.
-
C.
normIs
Indicates that something conforms to, or is characterized by, a particular standard, rule, or norm.
-
D.
hasNorm
Indicates that an entity is associated with, governed by, or characterized through a particular norm, rule, or standard.
-
E.
normType
Indicates the specific category or classification of a norm that governs or constrains an entity or situation.
- 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_69ca82e87f2c8190bdb71ee29dfc642d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fb995508190b2ca94ad45bf6d24 |
completed | March 31, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69cb70c3231c81909e3d463192c9de22 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:56 p.m.