Triple
T34102210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John 8:12 |
E874602
|
entity |
| Predicate | crossReferenceTheme |
P111150
|
FINISHED |
| Object | light imagery in John 1:4–9 |
—
|
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: light imagery in John 1:4–9 | Statement: [John 8:12, crossReferenceTheme, light imagery in John 1:4–9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossReferenceTheme Context triple: [John 8:12, crossReferenceTheme, light imagery in John 1:4–9]
-
A.
crossReference
chosen
Indicates that one entity refers the user to another related entity or source for additional or supporting information.
-
B.
coreThemeAssociation
Indicates a primary, central, or defining thematic relationship between two entities, where one serves as a core theme of the other.
-
C.
hasThemeRelationship
Indicates a relationship where one entity is thematically related to, or centered around, another entity as its main subject or topic.
-
D.
reflectsOnTheme
Indicates that one entity critically considers, analyzes, or comments on the theme expressed or embodied by another entity.
-
E.
usesThemeFrom
Indicates that one work incorporates, references, or is based on the thematic material of another work.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 1:53 a.m.