Triple
T4852977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orpah |
E108458
|
entity |
| Predicate | decisionContext |
P50766
|
FINISHED |
| Object | refuses to follow Naomi to 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: refuses to follow Naomi to Bethlehem | Statement: [Orpah, decisionContext, refuses to follow Naomi to Bethlehem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionContext Context triple: [Orpah, decisionContext, refuses to follow Naomi to Bethlehem]
-
A.
decisionLanguage
Indicates that a decision, statement, or choice is expressed or recorded in a particular natural language.
-
B.
decisionScope
Indicates the range or domain within which a particular decision is valid, applicable, or has authority.
-
C.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
-
D.
decisionDirection
chosen
Indicates the orientation or course (e.g., choice, stance, or path) that a decision takes relative to available options or influencing factors.
-
E.
decisionPublication
Indicates that a decision has been formally published or made publicly available.
- 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_69bd440a89548190a5f14ba6da6b97dc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2557388190a2d15571bacd24f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.