Triple
T4897233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Passion plays |
E109710
|
entity |
| Predicate | sometimesIncludesEvent |
P58905
|
FINISHED |
| Object | resurrection of Jesus |
—
|
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: resurrection of Jesus | Statement: [Passion plays, sometimesIncludesEvent, resurrection of Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesIncludesEvent Context triple: [Passion plays, sometimesIncludesEvent, resurrection of Jesus]
-
A.
includesEvents
chosen
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
-
B.
multiEventsIncluded
Indicates that multiple distinct events are collectively contained within, or form part of, a larger event set or grouping.
-
C.
participationIncludes
Indicates that a broader participation instance encompasses or contains a more specific participation instance as part of it.
-
D.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
-
E.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger 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_69bd4410bbf88190aad50d2451c863d6 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706245e48190a61d573438461c30 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c306b188190a08a7856beb76db4 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:28 p.m.