Triple
T16637757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1 Corinthians 11 |
E404251
|
entity |
| Predicate | containsQuotation |
P78667
|
FINISHED |
| Object | This is my body, which is for 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: This is my body, which is for you | Statement: [1 Corinthians 11, containsQuotation, This is my body, which is for you]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsQuotation Context triple: [1 Corinthians 11, containsQuotation, This is my body, which is for you]
-
A.
hasQuotationSystem
Indicates that an entity uses or is associated with a particular system or convention for representing quotations.
-
B.
hasQuotationStatus
Indicates that an entity has a particular quotation-related state or condition (such as being quoted, unquoted, or having a specific quotation status).
-
C.
quotationText
chosen
Indicates that the associated text is the exact content of a quotation made or referenced in the relationship.
-
D.
quotedOn
Indicates that one entity is cited, referenced, or mentioned within another source, document, or context.
-
E.
verseQuoted
Indicates that one text reproduces or cites a specific verse from another text.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e378eb07388190a10e896bae7f098e |
completed | April 18, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:18 a.m.