Triple
T917160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Ruth |
E19795
|
entity |
| Predicate | identifiesRuthAs |
P310
|
FINISHED |
| Object | Moabite woman |
—
|
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: Moabite woman | Statement: [Book of Ruth, identifiesRuthAs, Moabite woman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiesRuthAs Context triple: [Book of Ruth, identifiesRuthAs, Moabite woman]
-
A.
recognizedAs
chosen
Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
-
B.
roleInJudaism
Indicates the specific religious, social, or institutional function an entity holds within the context of Judaism.
-
C.
recognizesCreed
Indicates that one entity formally accepts or acknowledges the religious or ideological creed of another entity.
-
D.
babeRuthRole
Indicates that one entity serves in the specific role or capacity associated with Babe Ruth (e.g., as a legendary baseball player or iconic sports figure) in relation to another entity.
-
E.
identificationRole
Indicates that an entity serves as an identifier or plays a role in uniquely distinguishing or recognizing another entity.
- 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b6755c488190b7f7848110e3ea2c |
completed | March 1, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69a4b292d3408190947cbc2f794cf8c5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:39 p.m.