Triple
T10655146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | shooting of Pope John Paul II |
E251067
|
entity |
| Predicate | duringEvent |
P3824
|
FINISHED |
| Object | general audience |
—
|
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: general audience | Statement: [shooting of Pope John Paul II, duringEvent, general audience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: duringEvent Context triple: [shooting of Pope John Paul II, duringEvent, general audience]
-
A.
regionDuringEvent
Indicates that a specified region is associated with or exists within the spatial scope of a particular event during its occurrence.
-
B.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
C.
operatorDuringEvent
Indicates that an operator is actively performing their role or function throughout the duration of a specified event.
-
D.
occurredDuring
chosen
Indicates that one event or action took place within the temporal span of another event or time period.
-
E.
inForceDuringEvent
Indicates that a rule, condition, or state is actively valid and applicable throughout the duration of a specified 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dff94c188190b1a822c3720d18b7 |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:06 p.m.