Triple
T8153090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | From Eden |
E190376
|
entity |
| Predicate | featuresBiblicalImagery |
P4481
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [From Eden, featuresBiblicalImagery, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresBiblicalImagery Context triple: [From Eden, featuresBiblicalImagery, true]
-
A.
eschatologicalImagery
Indicates the use of symbolic or visionary imagery related to ultimate destiny, final judgment, or the end of the world.
-
B.
iconographicSubject
Indicates that one entity serves as the depicted subject or theme represented in the iconography of another entity.
-
C.
scripturalTheme
Indicates that one entity represents a central religious or theological theme expressed, discussed, or emphasized within a scriptural text or passage.
-
D.
scripturalAllusion
chosen
Indicates that one entity references, echoes, or draws upon content, themes, or language from a scriptural or sacred text in relation to another entity.
-
E.
shapeSymbolism
Indicates how a particular shape is associated with or conveys symbolic meaning within a given context.
- 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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb44d4494c8190aad2ee302e90670f |
completed | March 31, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:37 p.m.