Triple
T518489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christmastide |
E10759
|
entity |
| Predicate | theologyFocus |
P3095
|
FINISHED |
| Object | Incarnation |
—
|
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: Incarnation | Statement: [Christmastide, theologyFocus, Incarnation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theologyFocus Context triple: [Christmastide, theologyFocus, Incarnation]
-
A.
theologicalFocus
chosen
Indicates that something is primarily concerned with, centered on, or directed toward theological themes, questions, or doctrines.
-
B.
theologicalCategory
Indicates the classification of something according to a particular theological type, tradition, or doctrinal category.
-
C.
theologicalConcept
Indicates that something is a religious or theological idea, doctrine, or principle within a belief system.
-
D.
positionOnTheology
Indicates a stance, viewpoint, or opinion that one entity holds regarding theological beliefs, doctrines, or issues.
-
E.
theologicalTradition
Indicates the religious or doctrinal school, lineage, or system of belief within which an entity’s theology is developed or practiced.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f19ee6748190916603ef3a9e27f3 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f0151e8c81909a82b58ac0515eba |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.