Triple
T19082329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Covenant |
E467061
|
entity |
| Predicate | lawWritten |
P134288
|
FINISHED |
| Object | on believers’ hearts |
—
|
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: on believers’ hearts | Statement: [New Covenant, lawWritten, on believers’ hearts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lawWritten Context triple: [New Covenant, lawWritten, on believers’ hearts]
-
A.
legalAct
Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
-
B.
law
Indicates that one entity establishes, embodies, or enforces a rule or system of rules governing the behavior or relations of another entity.
-
C.
lawLibrary
Indicates a relationship where a location or resource functions as a library specifically dedicated to legal materials, services, or research.
-
D.
legalContent
Indicates that the associated material complies with applicable laws and regulations and is permitted for use, distribution, or display.
-
E.
legalBackground
Indicates that an entity has education, training, or experience related to law or the legal profession.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e9fccc819092c06c5da6f043ac |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.