Triple
T17612353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Temple period |
E428992
|
entity |
| Predicate | chronologicalAnchorEvent |
P72902
|
FINISHED |
| Object | destruction of Jerusalem in 586 BCE |
—
|
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: destruction of Jerusalem in 586 BCE | Statement: [First Temple period, chronologicalAnchorEvent, destruction of Jerusalem in 586 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalAnchorEvent Context triple: [First Temple period, chronologicalAnchorEvent, destruction of Jerusalem in 586 BCE]
-
A.
chronologicalPoint
Indicates that something is associated with, occurs at, or is anchored to a specific point in time within a chronological sequence.
-
B.
chronologyStartEvent
chosen
Indicates the event that marks the beginning or initial point in a chronological sequence or timeline.
-
C.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
D.
notableEventTime
Indicates the specific time at which a notable or significant event occurred.
-
E.
timeOfEventCommemorated
Indicates the specific time or date at which the event being commemorated originally occurred.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d2eaa348190a8226eef8c0d6e31 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.