Triple
T25301889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spirit of Detroit |
E634366
|
entity |
| Predicate | inscriptionContains |
P26405
|
FINISHED |
| Object | 2 Corinthians 3:17 |
—
|
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: 2 Corinthians 3:17 | Statement: [Spirit of Detroit, inscriptionContains, 2 Corinthians 3:17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionContains Context triple: [Spirit of Detroit, inscriptionContains, 2 Corinthians 3:17]
-
A.
inscriptionIncludesLine
chosen
Indicates that an inscription contains a specific line of text as one of its components.
-
B.
inscribedFor
Indicates that something is formally written, engraved, or dedicated for a particular recipient or purpose.
-
C.
inscriptionBy
Indicates that an inscription was created, written, or carved by a particular agent or entity.
-
D.
inscriptionUsedWith
Indicates that a particular inscription is employed together with, or in association with, another object, tool, or context in which it is applied or interpreted.
-
E.
inscription
Indicates that text has been written, carved, or engraved onto a surface or object.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f493968b5c8190bc0108a23b81b38a |
completed | May 1, 2026, 11:50 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:24 p.m.