Triple
T16717683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book XI (The City of God) |
E406265
|
entity |
| Predicate | beginsSection |
P54438
|
FINISHED |
| Object | second main part of The City 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: second main part of The City of God | Statement: [Book XI (The City of God), beginsSection, second main part of The City of God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beginsSection Context triple: [Book XI (The City of God), beginsSection, second main part of The City of God]
-
A.
sectionCreated
Indicates that a new section has been created or added within a larger structure, document, or system.
-
B.
section
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
C.
sectionIntroduced
Indicates that a particular section was introduced or added at a specific point in time or context.
-
D.
isOpeningSectionOf
chosen
Indicates that one content segment functions as the initial or introductory section of another, larger work or structure.
-
E.
extendedSection
Indicates that one section is a continuation or elaborated extension of another section.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3865799848190af919dccde958ee4 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.