Triple
T18968646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siloam Tunnel |
E464106
|
entity |
| Predicate | possibleBiblicalReference |
P11163
|
FINISHED |
| Object | 2 Kings 20:20 |
—
|
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: 2 Kings 20:20 | Statement: [Siloam Tunnel, possibleBiblicalReference, 2 Kings 20:20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleBiblicalReference Context triple: [Siloam Tunnel, possibleBiblicalReference, 2 Kings 20:20]
-
A.
scripturalReference
Indicates that one entity cites, alludes to, or is based on a specific passage or portion of a scriptural text found in another entity.
-
B.
scripturalBasis
Indicates that one entity serves as the religious or scriptural foundation, support, or justification for another entity (such as a belief, practice, or doctrine).
-
C.
inScripture
chosen
Indicates that something is mentioned, described, or referenced within a scriptural or sacred text.
-
D.
hasScripture
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
-
E.
receivedScripture
Indicates that one entity has been given or accepted a body of sacred or authoritative religious writings from another source.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d618e2ec8190848a41733e6db2f1 |
completed | April 20, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon