Triple
T262872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Catholicism |
E5787
|
entity |
| Predicate | originEvent |
P654
|
FINISHED |
| Object | opposition to Vatican I (1869–1870) |
—
|
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: opposition to Vatican I (1869–1870) | Statement: [Old Catholicism, originEvent, opposition to Vatican I (1869–1870)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originEvent Context triple: [Old Catholicism, originEvent, opposition to Vatican I (1869–1870)]
-
A.
basedOnEvent
Indicates that something is derived from, influenced by, or determined in reference to a specific event.
-
B.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
-
C.
introducedEvent
Indicates that an entity is responsible for bringing an event into existence or initiating it for the first time.
-
D.
formationEvent
chosen
Indicates the event or process through which something comes into existence, is created, or is initially established.
-
E.
shapedByEvent
Indicates that something’s form, state, or characteristics are influenced or determined by a particular event.
- 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_69a258dd8ea08190ac554a1cc8dfd8c3 |
completed | Feb. 28, 2026, 2:54 a.m. |
| NER | Named-entity recognition | batch_69a25d8c7f448190af9145256f994177 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6e07748190834022a65ba6d803 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.