Triple
T2279044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parable of the Good Samaritan |
E51237
|
entity |
| Predicate | concludesWithCommand |
P22505
|
FINISHED |
| Object | Go and do likewise |
—
|
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: Go and do likewise | Statement: [Parable of the Good Samaritan, concludesWithCommand, Go and do likewise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concludesWithCommand Context triple: [Parable of the Good Samaritan, concludesWithCommand, Go and do likewise]
-
A.
containsCommand
chosen
Indicates that one entity includes or embeds a command directed at or executable by another entity.
-
B.
concludedWith
Indicates that an event, process, or interaction ended or was finalized by a specific outcome, action, or state.
-
C.
concludes
Indicates that one entity brings something (such as an event, process, or discussion) to an end or reaches a final decision or judgment about it.
-
D.
hasCommand
Indicates that one entity possesses, controls, or is associated with a specific command or directive applied to another entity or process.
-
E.
endedWith
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc2194150819083156e4dcd45a423 |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.