Triple
T157312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last Supper |
E3206
|
entity |
| Predicate | timeRelativeToCrucifixion |
P2325
|
FINISHED |
| Object | evening before the crucifixion 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: evening before the crucifixion of Jesus | Statement: [Last Supper, timeRelativeToCrucifixion, evening before the crucifixion of Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeRelativeToCrucifixion Context triple: [Last Supper, timeRelativeToCrucifixion, evening before the crucifixion of Jesus]
-
A.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
B.
dateOfBurial
Indicates the specific date on which an entity was buried.
-
C.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
D.
timeNotation
Indicates the specific system or format used to represent and write times (e.g., 12-hour vs 24-hour notation).
-
E.
timeDescribedAs
chosen
Indicates that a specific time or temporal interval is characterized, labeled, or expressed using a particular description or representation.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a25830136881909f5ecb2cb22097b2 |
completed | Feb. 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69a2565f30848190a2a71fdb7dc140b5 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.