Triple
T19723567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Am That I Am |
E473666
|
entity |
| Predicate | VulgateRendering |
P22307
|
FINISHED |
| Object | Ego sum qui sum |
—
|
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: Ego sum qui sum | Statement: [I Am That I Am, VulgateRendering, Ego sum qui sum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: VulgateRendering Context triple: [I Am That I Am, VulgateRendering, Ego sum qui sum]
-
A.
basedOnEditionOfVulgate
chosen
Indicates that something is derived from, adapted from, or otherwise based on a particular edition of the Vulgate text.
-
B.
renderedUnder
Indicates that one entity was produced, displayed, or executed within the authority, context, or environment provided by another entity.
-
C.
numberingInSeptuagintVulgate
Indicates that the entity uses the chapter or verse numbering system as found in the Septuagint and Vulgate traditions.
-
D.
notableRendering
Indicates that one entity is a significant or well-known visual or artistic depiction of another entity.
-
E.
renderingMode
Indicates the specific way in which content or graphics are processed and displayed (e.g., style, technique, or pipeline used for rendering).
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649f64984819097882c44098b1643 |
completed | April 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:46 p.m.