Triple
T12558795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verbum in Ecclesia |
E295285
|
entity |
| Predicate | isSubsequentTo |
P6880
|
FINISHED |
| Object | synodal propositions on the Word 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: synodal propositions on the Word of God | Statement: [Verbum in Ecclesia, isSubsequentTo, synodal propositions on the Word of God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubsequentTo Context triple: [Verbum in Ecclesia, isSubsequentTo, synodal propositions on the Word of God]
-
A.
hasSubsequent
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
-
B.
isSuccessorTo
Indicates that one entity directly follows another in an ordered sequence, coming immediately after it.
-
C.
cededTo
Indicates that control, ownership, or authority over something was formally transferred from one entity to another.
-
D.
chronologicallyAfter
chosen
Indicates that one event or state occurs later in time than another.
-
E.
governsAfter
Indicates that one entity assumes governing authority or control after another entity’s period of governance has ended.
- 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 11:48 p.m.