Triple
T742392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maccabean Revolt |
E15270
|
entity |
| Predicate | hasDateOfTempleRededication |
P3370
|
FINISHED |
| Object | 25 Kislev |
—
|
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: 25 Kislev | Statement: [Maccabean Revolt, hasDateOfTempleRededication, 25 Kislev]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDateOfTempleRededication Context triple: [Maccabean Revolt, hasDateOfTempleRededication, 25 Kislev]
-
A.
rededicationDate
chosen
Indicates the date on which something is formally dedicated again, typically after restoration, change, or renewal.
-
B.
lastMajorTempleClosed
Indicates the time or event at which the final significant temple associated with an entity was permanently closed.
-
C.
consecrationDate
Indicates the date on which something (typically a building, object, or person) was formally dedicated or made sacred through a religious or ceremonial act.
-
D.
reconstructionOrRestorationDate
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
-
E.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a60e286c81908787a41cf9b9f150 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fdaaf48190985f62acfc069508 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.