Triple
T19748346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Divine Maternity of Mary |
E474311
|
entity |
| Predicate | hasDoctrinalTitle |
P65893
|
FINISHED |
| Object | Mother of God |
—
|
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: Mother of God | Statement: [Divine Maternity of Mary, hasDoctrinalTitle, Mother of God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDoctrinalTitle Context triple: [Divine Maternity of Mary, hasDoctrinalTitle, Mother of God]
-
A.
hasDoctrinalStandardInPart
Indicates that one entity possesses or upholds a specific doctrinal standard within a particular section or component of itself.
-
B.
hasTitleIn
chosen
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
C.
hasDoctrinalBasis
Indicates that one concept, claim, or practice is grounded in, supported by, or derived from a specific doctrine or set of doctrines.
-
D.
hasTitleSubject
Indicates that an entity has a specific subject or topic as the focus of its title.
-
E.
hasDoctrinalCharacteristic
Indicates that an entity possesses a specific doctrinal feature, quality, or attribute within a belief or teaching system.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65295f3b88190a541354f41e3ea1d |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.