Triple
T7290913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ut Unum Sint |
E164388
|
entity |
| Predicate | biblicalMotto |
P36775
|
FINISHED |
| Object | “that they may all be one” (John 17:21) |
—
|
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: “that they may all be one” (John 17:21) | Statement: [Ut Unum Sint, biblicalMotto, “that they may all be one” (John 17:21)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biblicalMotto Context triple: [Ut Unum Sint, biblicalMotto, “that they may all be one” (John 17:21)]
-
A.
scripturalMotto
chosen
Indicates that one entity serves as the official scriptural or religiously inspired motto or guiding phrase associated with another entity.
-
B.
mottoInterpretation
Indicates the explanatory relationship between a motto and its intended meaning or message.
-
C.
mottoType
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
D.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
E.
isMottoOf
Indicates that a phrase or expression serves as the official motto associated with a particular 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb6e8f3881908628b3d41aad70c6 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76c5fbc8190b378830082f11cb0 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3 p.m.