Triple
T37424505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feast of Our Lady of Lourdes |
E929951
|
entity |
| Predicate | connectedToDogma |
P137172
|
FINISHED |
| Object | dogma of the Immaculate Conception |
—
|
NE NERFINISHED |
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 of the Immaculate Conception | Statement: [Feast of Our Lady of Lourdes, connectedToDogma, dogma of the Immaculate Conception]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToDogma Context triple: [Feast of Our Lady of Lourdes, connectedToDogma, dogma of the Immaculate Conception]
-
A.
connectedDogmaProclaimedOn
Indicates that a particular dogma is formally linked to and proclaimed on a specific date or occasion.
-
B.
linkedDogmaDocument
Indicates that one entity is associated with or references a specific dogma-related document as a linked resource.
-
C.
relatedDogma
chosen
Indicates that one doctrine, belief, or dogma is conceptually or thematically connected to another.
-
D.
isDefinedAsDogmaBy
Indicates that one entity formally establishes or declares another entity as dogma or authoritative doctrine.
-
E.
sharesDogmaWith
Indicates that two entities hold and adhere to the same set of core beliefs, doctrines, or ideological principles.
- 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffe613c03481909f3043ec8bf0bed9 |
completed | May 10, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69ffe4a73fb4819091600725a443981a |
completed | May 10, 2026, 1:51 a.m. |
Created at: May 3, 2026, 4:16 p.m.