Triple
T943434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annunciation |
E20356
|
entity |
| Predicate | announcedTitleOfJesus |
P8467
|
FINISHED |
| Object | Son of the Most High |
—
|
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: Son of the Most High | Statement: [Annunciation, announcedTitleOfJesus, Son of the Most High]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedTitleOfJesus Context triple: [Annunciation, announcedTitleOfJesus, Son of the Most High]
-
A.
announcedThat
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
-
B.
announcedAs
chosen
Indicates that one entity is publicly presented, declared, or introduced in a specified role, name, or capacity by another entity.
-
C.
reportedTitleOfMary
Indicates that the specified title is one that has been reported or recorded as belonging to Mary.
-
D.
wasProclaimed
Indicates that an entity was formally announced, declared, or made official, typically through an authoritative or ceremonial proclamation.
-
E.
hadTitle
Indicates that an entity held or was assigned a specific title or formal designation.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3a2b1ec8190a2753ad3b3e8cc7a |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b29dc8dc8190b9d33f70f8563d61 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.