Triple
T24175683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary as Mediatrix |
E599275
|
entity |
| Predicate | notDefinedAs |
P23080
|
FINISHED |
| Object | dogma by the Catholic Church |
—
|
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: dogma by the Catholic Church | Statement: [Mary as Mediatrix, notDefinedAs, dogma by the Catholic Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notDefinedAs Context triple: [Mary as Mediatrix, notDefinedAs, dogma by the Catholic Church]
-
A.
notDescribedAs
Indicates that an entity is explicitly not characterized, labeled, or referred to using a particular description or term.
-
B.
notDefinedPrimarilyBy
Indicates that one entity is not chiefly or fundamentally characterized, identified, or determined by another entity or attribute.
-
C.
doesNotDefine
chosen
Indicates that one entity does not provide a definition, specification, or determining description for another entity.
-
D.
notResolvedBy
Indicates that an issue, problem, or request remains unresolved despite the involvement or actions of a specified entity.
-
E.
notClassifiedAs
Indicates that an entity is explicitly not assigned to, or excluded from, a particular class or category.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:34 p.m.