Triple
T3725507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Micah |
E81737
|
entity |
| Predicate | messianicTheme |
P13857
|
FINISHED |
| Object | ruler from Bethlehem |
—
|
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: ruler from Bethlehem | Statement: [Book of Micah, messianicTheme, ruler from Bethlehem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: messianicTheme Context triple: [Book of Micah, messianicTheme, ruler from Bethlehem]
-
A.
messianicFigureAssociated
Indicates a relationship in which a person, symbol, or concept is linked or connected to a messianic figure, role, or expectation.
-
B.
viewOfMessianicAge
Indicates a belief or depiction of how the prophesied messianic era will look or unfold.
-
C.
subjectOfProphecy
Indicates that the subject is foretold or predicted to play a significant role or experience a specific event according to a prophecy.
-
D.
viewOnMessiah
Indicates the stance, belief, or doctrinal position an entity holds regarding the Messiah.
-
E.
scripturalTheme
chosen
Indicates that one entity represents a central religious or theological theme expressed, discussed, or emphasized within a scriptural text or passage.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf669d48190852aaeef70265404 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.