Triple
T25073920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hosea 2:23 |
E627995
|
entity |
| Predicate | reversesPronouncement |
P158399
|
FINISHED |
| Object | Lo-ammi (Not My People) |
—
|
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: Lo-ammi (Not My People) | Statement: [Hosea 2:23, reversesPronouncement, Lo-ammi (Not My People)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reversesPronouncement Context triple: [Hosea 2:23, reversesPronouncement, Lo-ammi (Not My People)]
-
A.
reversed
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
-
B.
pronouncementsForm
Indicates that one entity constitutes or makes up the pronouncements, declarations, or formal statements of another entity.
-
C.
reverseInscription
Indicates that one entity is inscribed as the reverse or mirror image of another entity’s inscription.
-
D.
hasPronunciationDifferenceFrom
Indicates that two linguistic items differ in how they are pronounced.
-
E.
avoidsPronunciationOf
Indicates that one entity deliberately refrains from saying or articulating the name, word, or expression associated with another entity.
- F. None of above. chosen
Provenance (4 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46d3f35848190b56a4373c97a7d64 |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 18, 2026, 6:20 a.m.