Triple
T9822974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book 16 (The City of God) |
E238580
|
entity |
| Predicate | locatedInSequence |
P4527
|
FINISHED |
| Object | second half 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 half of The City of God | Statement: [Book 16 (The City of God), locatedInSequence, second half of The City of God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInSequence Context triple: [Book 16 (The City of God), locatedInSequence, second half of The City of God]
-
A.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
locatedAfter
chosen
Indicates that one entity is positioned later than another along a defined sequence, order, or spatial/temporal axis.
-
C.
placedInOrderBy
Indicates that one entity was arranged or positioned according to a sequence or priority determined by another entity.
-
D.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
-
E.
locatedBetween
Indicates that one entity is positioned spatially between two other reference entities.
- 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.