Triple
T34420101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beatissime Pater |
E883501
|
entity |
| Predicate | beatissimeMeaning |
P92178
|
FINISHED |
| Object | most blessed |
—
|
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: most blessed | Statement: [Beatissime Pater, beatissimeMeaning, most blessed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beatissimeMeaning Context triple: [Beatissime Pater, beatissimeMeaning, most blessed]
-
A.
containsBeatitude
Indicates that one entity includes or embodies a state of blessedness, spiritual happiness, or divine favor in relation to another.
-
B.
basicMeaning
chosen
Indicates that one entity expresses or conveys the fundamental or core meaning of another entity.
-
C.
b2Meaning
Indicates that one entity represents the underlying meaning, sense, or semantic content associated with another entity.
-
D.
b1Meaning
Indicates that one entity represents the primary or first meaning or interpretation associated with another entity.
-
E.
sapereMeaning
Indicates that one entity knows, understands, or is aware of the meaning or sense of another entity.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71947ad88819082ab9d85dd493b01 |
completed | May 3, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.