Triple
T35845284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domina Nostra |
E1036189
|
entity |
| Predicate | Dominus NosterMeaning |
P80782
|
FINISHED |
| Object | Our 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: Our Lord | Statement: [Domina Nostra, Dominus NosterMeaning, Our Lord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Dominus NosterMeaning Context triple: [Domina Nostra, Dominus NosterMeaning, Our Lord]
-
A.
InNomineDominiContent
Indicates that the content is presented, declared, or performed "in the name of the Lord," invoking divine authority or dedication.
-
B.
InNomineDominiEffect
Indicates an effect or outcome that occurs specifically by invoking, acting under, or being empowered by the name or authority of the Lord.
-
C.
FidelisMeaning
Indicates that one entity embodies or conveys the meaning, sense, or definition of another entity in a faithful or accurate way.
-
D.
oniMeaning
chosen
Indicates that one entity expresses or conveys the meaning or sense of another entity (such as a word, phrase, or symbol).
-
E.
MorsMeaning
Indicates a relationship where one entity conveys, embodies, or defines the meaning or significance of another.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.