Triple
T23463486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apostolic constitutions |
E569043
|
entity |
| Predicate | oftenBeginWith |
P12097
|
FINISHED |
| Object | solemn invocations or formulas |
—
|
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: solemn invocations or formulas | Statement: [Apostolic constitutions, oftenBeginWith, solemn invocations or formulas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenBeginWith Context triple: [Apostolic constitutions, oftenBeginWith, solemn invocations or formulas]
-
A.
beganWith
chosen
Indicates that one event, process, or state started with or was initiated by another specified event, process, or state.
-
B.
endsUpWith
Indicates that, as a result of some process or sequence of events, one entity ultimately comes to possess, receive, or be associated with another entity.
-
C.
precededByCapital
Indicates that the referenced element is immediately preceded by a capital letter.
-
D.
usesConsonantInitials
Indicates that an entity’s initials or abbreviated form begin with consonant letters rather than vowels.
-
E.
oftenPrecededBy
Indicates that one event, state, or item commonly occurs or appears before another in time or sequence.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a69f0a54819084c19c248a572253 |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:54 p.m.