Triple
T35581119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis 9 |
E1028224
|
entity |
| Predicate | setsLaw |
P116428
|
FINISHED |
| Object | prohibition of shedding human blood |
—
|
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: prohibition of shedding human blood | Statement: [Genesis 9, setsLaw, prohibition of shedding human blood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsLaw Context triple: [Genesis 9, setsLaw, prohibition of shedding human blood]
-
A.
containsLaw
chosen
Indicates that one entity (such as a document, code, or jurisdiction) includes or encompasses a specific law within it.
-
B.
stateOfLaw
Indicates that a specified legal condition, rule, or status is currently in force or applicable within a given jurisdiction or context.
-
C.
haveLaw
Indicates that a governing body or jurisdiction possesses, enforces, or is characterized by a particular law or set of laws.
-
D.
usesLawTo
Indicates that one entity applies or relies on a specific law as a means or tool to affect, regulate, or influence another entity or situation.
-
E.
legalSetting
Indicates that an entity is involved in, occurs within, or is characterized by a formal legal context, such as courts, legal procedures, or judicial environments.
- 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_69f76e0495a081909beced418558c0b4 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.