Triple
T1716811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Commandment |
E37307
|
entity |
| Predicate | secondCommand |
P25127
|
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: [Great Commandment, secondCommand, love your neighbor as yourself]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondCommand Context triple: [Great Commandment, secondCommand, love your neighbor as yourself]
-
A.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
B.
secondWord
Indicates that one entity is the second word in sequence immediately following the first entity in a text or utterance.
-
C.
secondWork
Indicates that one work is the second in order relative to another work within a sequence or set.
-
D.
secondStage
chosen
Indicates that something functions as the subsequent or follow-up stage in a multi-stage process or sequence.
-
E.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab5c96db6c8190a745d6fef7bf2cdb |
completed | March 6, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69aa61bed2fc819086d912cd34285978 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.