Triple
T31271038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O Grave, Where Is Thy Victory |
E797385
|
entity |
| Predicate | hasTitleSource |
P184604
|
FINISHED |
| Object | 1 Corinthians 15:55 |
—
|
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: 1 Corinthians 15:55 | Statement: [O Grave, Where Is Thy Victory, hasTitleSource, 1 Corinthians 15:55]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleSource Context triple: [O Grave, Where Is Thy Victory, hasTitleSource, 1 Corinthians 15:55]
-
A.
hasTitleInSources
chosen
Indicates that an entity is associated with a specific title as it appears in one or more referenced sources.
-
B.
hasTitleFrom
Indicates that one entity holds or uses a title that originates from, or is conferred by, another entity.
-
C.
hasTitleType
Indicates that an entity holds a specific kind or category of title (such as job title, honorific, or formal designation).
-
D.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
E.
hasTitleName
Indicates that an entity possesses or is associated with a specific title or name.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 29, 2026, 9:13 p.m.