Triple
T34249696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Baptism |
E878704
|
entity |
| Predicate | underscoresEvent |
P192668
|
FINISHED |
| Object | baptism of Michael Corleone’s nephew |
—
|
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: baptism of Michael Corleone’s nephew | Statement: [The Baptism, underscoresEvent, baptism of Michael Corleone’s nephew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underscoresEvent Context triple: [The Baptism, underscoresEvent, baptism of Michael Corleone’s nephew]
-
A.
impliesEvent
Indicates that one event logically leads to, entails, or guarantees the occurrence of another event.
-
B.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
-
C.
suppressedAfterEvent
Indicates that something is intentionally hidden, blocked, or prevented from occurring after a specified event has taken place.
-
D.
exposesEvent
Indicates that one entity makes an event available or visible for use, handling, or observation by another entity or system.
-
E.
interpretsEvent
Indicates that an entity analyzes and assigns meaning or significance to an event.
- F. None of above. chosen
Provenance (4 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_69f349b3618481909df955b063f305b2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: May 1, 2026, 1:56 a.m.