Triple
T94363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sermon on the Mount |
E1895
|
entity |
| Predicate | canonicalStatus |
P3927
|
FINISHED |
| Object | Part of the Christian biblical canon |
—
|
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: Part of the Christian biblical canon | Statement: [Sermon on the Mount, canonicalStatus, Part of the Christian biblical canon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalStatus Context triple: [Sermon on the Mount, canonicalStatus, Part of the Christian biblical canon]
-
A.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
B.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
C.
hasIconicStatus
Indicates that an entity holds a widely recognized, emblematic, or culturally significant status within a particular domain or context.
-
D.
standardizedBy
Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
-
E.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
- F. None of above. chosen
Provenance (4 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a24feef1b08190bb9525f71cce053e |
completed | Feb. 28, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69a24ebb3da08190a8b82564f33cde3b |
completed | Feb. 28, 2026, 2:11 a.m. |
| PDg | Predicate description generation | batch_69a24fed6b8c819080a6c0cd3b16e6bd |
completed | Feb. 28, 2026, 2:16 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.