Triple
T189936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Orders |
E3696
|
entity |
| Predicate | isClassifiedAs |
P310
|
FINISHED |
| Object | sacrament at the service of communion |
—
|
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: sacrament at the service of communion | Statement: [Holy Orders, isClassifiedAs, sacrament at the service of communion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClassifiedAs Context triple: [Holy Orders, isClassifiedAs, sacrament at the service of communion]
-
A.
hasLCClassification
Indicates that an entity is assigned a specific Library of Congress Classification code representing its subject or shelving category.
-
B.
isGradeOf
Indicates that one entity is the grade or evaluation assigned to another entity, such as a student, assignment, or performance.
-
C.
recognizedAs
chosen
Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
-
D.
classificationStart
Indicates the point in time or process at which a classification or categorization of an entity begins.
-
E.
securityClassification
Indicates the level or category of security sensitivity or access restriction assigned to an 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a2594c385481909e1e088e45c460a4 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25673ce3c8190b1a3df5b814a0595 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.