Triple
T5843090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tabernacle of David |
E129639
|
entity |
| Predicate | propheticReference |
P22416
|
FINISHED |
| Object | Amos 9:11 |
—
|
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: Amos 9:11 | Statement: [Tabernacle of David, propheticReference, Amos 9:11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propheticReference Context triple: [Tabernacle of David, propheticReference, Amos 9:11]
-
A.
subjectOfProphecy
chosen
Indicates that the subject is foretold or predicted to play a significant role or experience a specific event according to a prophecy.
-
B.
prophecyKnownAs
Indicates that a particular prophecy is referred to or recognized by a specific name or title.
-
C.
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.
-
D.
prophecyMade
Indicates that a prophetic statement or prediction has been declared by one entity concerning a future event or outcome involving another entity.
-
E.
propheticActivity
Indicates engaging in or being associated with acts of prophecy, such as receiving, delivering, or performing messages believed to be divinely inspired.
- 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_69c0084bd31c8190a796bb6284845e83 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.