Triple
T10818514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Youth Day 1987 |
E255296
|
entity |
| Predicate | themeBiblicalReference |
P13857
|
FINISHED |
| Object | 1 John 4:16 |
—
|
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: 1 John 4:16 | Statement: [World Youth Day 1987, themeBiblicalReference, 1 John 4:16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeBiblicalReference Context triple: [World Youth Day 1987, themeBiblicalReference, 1 John 4:16]
-
A.
scripturalTheme
chosen
Indicates that one entity represents a central religious or theological theme expressed, discussed, or emphasized within a scriptural text or passage.
-
B.
themeInQuran
Indicates that a particular theme, concept, or topic is present in and addressed by the Quran.
-
C.
scriptureFocus
Indicates that something centers on, emphasizes, or is primarily concerned with religious scripture or sacred texts.
-
D.
scriptureFor
Indicates that one entity serves as a scriptural or authoritative religious text for another entity (such as a person, group, or belief system).
-
E.
scriptureAllusion
Indicates that one entity makes reference to, echoes, or is inspired by a passage, theme, or element from a scriptural text found in 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7344866f88190be4addb7c8020fce |
completed | April 9, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:18 p.m.