Triple

T19812927
Position Surface form Disambiguated ID Type / Status
Subject Non nobis Domine, non nobis, sed nomini tuo da gloriam E475989 entity
Predicate invokesNameOf P57113 FINISHED
Object Dominus (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: Dominus (the Lord) | Statement: [Non nobis Domine, non nobis, sed nomini tuo da gloriam, invokesNameOf, Dominus (the Lord)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: invokesNameOf
Context triple: [Non nobis Domine, non nobis, sed nomini tuo da gloriam, invokesNameOf, Dominus (the Lord)]
  • A. importName
    Indicates that one entity brings another entity into a scope, module, or context under a specific name used for reference.
  • B. invocationOf chosen
    Indicates that one entity is the act, event, or instance of calling upon, summoning, or appealing to another entity (such as a function, service, or authority) to perform its role or be brought into effect.
  • C. nameOf
    Indicates that one entity is the name or designation of another entity.
  • D. exportName
    Indicates that one entity is exported under a specific name or label in relation to another context or system.
  • E. namedAs
    Indicates that one entity is given, known by, or referred to using the name 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_69d8e51bc4208190a1c57d8c5d1b15e4 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6542d7c048190818359cbf430f50e completed April 20, 2026, 4:28 p.m.
PD Predicate disambiguation batch_69e5305858108190bbbfdb9ba3ab9f80 completed April 19, 2026, 7:43 p.m.
Created at: April 10, 2026, 1:50 p.m.