Triple
T4918226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leviticus 19 |
E110398
|
entity |
| Predicate | centralCommand |
P60018
|
FINISHED |
| Object | love your neighbor as yourself |
—
|
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: love your neighbor as yourself | Statement: [Leviticus 19, centralCommand, love your neighbor as yourself]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralCommand Context triple: [Leviticus 19, centralCommand, love your neighbor as yourself]
-
A.
coreCommand
Indicates that one entity serves as the primary or central command or control authority over another entity or process.
-
B.
commandOf
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
-
C.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
D.
firstCommand
Indicates that one entity is the initial or earliest command issued in a sequence of commands associated with another entity.
-
E.
commandedBy
Indicates that one entity holds authoritative control or issues orders over 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6fa760448190946401b4b21ea8b7 |
completed | March 20, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6e482984819087124216738f1e29 |
completed | March 20, 2026, 3:56 p.m. |
Created at: March 20, 2026, 1:29 p.m.