Triple
T11496802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Exile |
E272554
|
entity |
| Predicate | finalVersesFeature |
P45564
|
FINISHED |
| Object | multiple names and attributes of God |
—
|
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: multiple names and attributes of God | Statement: [The Exile, finalVersesFeature, multiple names and attributes of God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalVersesFeature Context triple: [The Exile, finalVersesFeature, multiple names and attributes of God]
-
A.
containsVerse
Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
-
B.
closingVerse
Indicates that one entity serves as the final or concluding verse of another entity, such as a song, poem, or hymn.
-
C.
verses
Indicates a relationship where one entity competes or is pitted against another, as in an opposition, matchup, or comparison.
-
D.
finalVersesPromise
chosen
Indicates that a promise or commitment is expressed or affirmed in the final verses of a text or discourse.
-
E.
featuresSpokenVerses
Indicates that something includes or presents spoken verses as a notable component or element.
- 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85de183f08190abfa36eaabc61dc6 |
completed | April 10, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.