Triple
T2365339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon 1 |
E47364
|
entity |
| Predicate | setsNormsFor |
P12028
|
FINISHED |
| Object | acceptance of orthodox doctrine |
—
|
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: acceptance of orthodox doctrine | Statement: [Canon 1, setsNormsFor, acceptance of orthodox doctrine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsNormsFor Context triple: [Canon 1, setsNormsFor, acceptance of orthodox doctrine]
-
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.
hasNorm
Indicates that an entity is associated with, governed by, or characterized through a particular norm, rule, or standard.
-
C.
normIs
Indicates that something conforms to, or is characterized by, a particular standard, rule, or norm.
-
D.
normType
Indicates the specific category or classification of a norm that governs or constrains an entity or situation.
-
E.
setsRulesFor
Indicates that one entity establishes or defines rules, guidelines, or constraints that another entity is expected to follow.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc7486cb48190acef1891cc87bdb1 |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc599b92c819093d9e15d4437705d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:55 p.m.