Triple
T15726248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noahic covenant |
E381224
|
entity |
| Predicate | commandIncludes |
P22505
|
FINISHED |
| Object | be fruitful and multiply |
—
|
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: be fruitful and multiply | Statement: [Noahic covenant, commandIncludes, be fruitful and multiply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandIncludes Context triple: [Noahic covenant, commandIncludes, be fruitful and multiply]
-
A.
containsCommand
chosen
Indicates that one entity includes or embeds a command directed at or executable by another entity.
-
B.
programIncluded
Indicates that a particular program is contained within, or forms part of, another specified collection, package, or set of programs.
-
C.
outputIncludes
Indicates that the result or product of a process, function, or action contains or incorporates a specified element or component.
-
D.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
E.
commandOf
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb357a88190a92641c8a8c20573 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.