Triple
T30084729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A New Commandment |
E764571
|
entity |
| Predicate | hasTextIncipit |
P67696
|
FINISHED |
| Object | A new commandment I give unto you |
—
|
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: A new commandment I give unto you | Statement: [A New Commandment, hasTextIncipit, A new commandment I give unto you]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTextIncipit Context triple: [A New Commandment, hasTextIncipit, A new commandment I give unto you]
-
A.
hasLatinIncipit
Indicates that an entity begins with, or is identified by, a specified Latin opening phrase (incipit).
-
B.
hasEnglishIncipit
chosen
Indicates that an entity has an opening phrase or initial text (incipit) expressed in English.
-
C.
hasText
Indicates that an entity is associated with or contains a specific piece of textual content.
-
D.
hasTextBy
Indicates that one entity (such as a document, work, or record) contains or is associated with text authored or written by another entity.
-
E.
hasTextFrom
Indicates that one entity contains, is derived from, or directly uses the textual content originating from another entity.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 29, 2026, 7:03 p.m.