Triple
T9822948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book 6 (The City of God) |
E238579
|
entity |
| Predicate | continuesThemeOf |
P22147
|
FINISHED |
| Object | critique of pagan religion |
—
|
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: critique of pagan religion | Statement: [Book 6 (The City of God), continuesThemeOf, critique of pagan religion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuesThemeOf Context triple: [Book 6 (The City of God), continuesThemeOf, critique of pagan religion]
-
A.
followsInTheme
chosen
Indicates that one element continues or succeeds another while maintaining the same theme or thematic context.
-
B.
followsTheme
Indicates that one entity adheres to, is guided by, or is structured according to the theme established by another entity.
-
C.
successorTheme
Indicates that one theme follows, replaces, or continues another theme in a sequence or progression.
-
D.
continuedBy
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
-
E.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
- 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_69ca84e0dd1881909800765d1e21f735 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb315ddf48190bd90f7835f409bb6 |
completed | April 2, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:31 p.m.