Triple
T7199904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lectionary for Mass |
E168712
|
entity |
| Predicate | normedBy |
P1371
|
FINISHED |
| Object | General Introduction to the Lectionary |
—
|
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: General Introduction to the Lectionary | Statement: [Lectionary for Mass, normedBy, General Introduction to the Lectionary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: normedBy Context triple: [Lectionary for Mass, normedBy, General Introduction to the Lectionary]
-
A.
normIs
Indicates that something conforms to, or is characterized by, a particular standard, rule, or norm.
-
B.
hasNorm
Indicates that an entity is associated with, governed by, or characterized through a particular norm, rule, or standard.
-
C.
normType
Indicates the specific category or classification of a norm that governs or constrains an entity or situation.
-
D.
normativeFor
Indicates that something establishes, prescribes, or encodes the norms, standards, or rules that should govern another thing’s behavior or state.
-
E.
standardizedBy
chosen
Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
- 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e92cc8ac8190a6448b79496a8249 |
completed | March 27, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:52 p.m.