Triple
T4767812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visitation |
E105854
|
entity |
| Predicate | MaryStatusRecognizedAs |
P37237
|
FINISHED |
| Object | mother of the Lord |
—
|
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 the Lord | Statement: [Visitation, MaryStatusRecognizedAs, mother of the Lord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MaryStatusRecognizedAs Context triple: [Visitation, MaryStatusRecognizedAs, mother of the Lord]
-
A.
recognitionStatus
Indicates the current state or outcome of acknowledging, validating, or officially accepting something or someone.
-
B.
areRecognizedBy
chosen
Indicates that one entity acknowledges, identifies, or accepts another entity as valid, known, or legitimate.
-
C.
identityStatus
Indicates the current state or condition of an entity’s identity, such as whether it is verified, active, pending, or otherwise classified.
-
D.
mintStatusGranted
Indicates that an entity has been officially authorized or approved to mint (create or issue) something, such as tokens, assets, or items.
-
E.
recognizedThrough
Indicates that something becomes known, identified, or acknowledged by means of a particular method, medium, or process.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.