Triple
T16816913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1 Corinthians 9 |
E408774
|
entity |
| Predicate | literaryContextPrecededBy |
P62381
|
FINISHED |
| Object | 1 Corinthians 8 |
—
|
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 8 | Statement: [1 Corinthians 9, literaryContextPrecededBy, 1 Corinthians 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryContextPrecededBy Context triple: [1 Corinthians 9, literaryContextPrecededBy, 1 Corinthians 8]
-
A.
literaryPredecessor
chosen
Indicates that one work of literature precedes and influences another in a historically or artistically significant way.
-
B.
hasLiteraryContext
Indicates that something is associated with, situated within, or explained by a particular literary context (such as a work, genre, period, or interpretive framework).
-
C.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
D.
precededByDocument
Indicates that one document occurs or is issued earlier in sequence or time than another document.
-
E.
literarySource
Indicates that one entity serves as the written or literary origin, reference, or basis for 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e30cf48190a61936ba0a49df24 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.