Triple
T19093650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Innocents |
E467350
|
entity |
| Predicate | propheticallyLinkedTo |
P116863
|
FINISHED |
| Object | Jeremiah 31:15 |
—
|
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: Jeremiah 31:15 | Statement: [Holy Innocents, propheticallyLinkedTo, Jeremiah 31:15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propheticallyLinkedTo Context triple: [Holy Innocents, propheticallyLinkedTo, Jeremiah 31:15]
-
A.
linkedToProphet
Indicates a relationship in which an entity is associated or connected in some meaningful way to a prophet.
-
B.
prophetAmong
Indicates that one entity serves as a prophet within, or in relation to, a particular group, community, or people represented by the other entity.
-
C.
relatedProphecy
chosen
Indicates that there exists a prophetic connection or foretelling relationship between the entities involved.
-
D.
prophecyHeardBy
Indicates that a prophecy was heard or received by a particular entity.
-
E.
subjectOfProphecy
Indicates that the subject is foretold or predicted to play a significant role or experience a specific event according to a prophecy.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e34cf5e481908e1f180dacd5602f |
completed | April 20, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.