Triple
T113404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman destruction of the Second Temple |
E2292
|
entity |
| Predicate | militaryAction |
P12
|
FINISHED |
| Object | siege of Jerusalem |
—
|
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: siege of Jerusalem | Statement: [Roman destruction of the Second Temple, militaryAction, siege of Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryAction Context triple: [Roman destruction of the Second Temple, militaryAction, siege of Jerusalem]
-
A.
militaryConflict
chosen
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
B.
militaryTheater
Indicates that an entity is a geographic or operational area where military operations or campaigns are conducted.
-
C.
warfareType
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
D.
militaryStrategy
Indicates a relationship where an entity plans, directs, or is associated with the organized use of armed forces and tactics to achieve military or defense objectives.
-
E.
SovietAction
Indicates actions, policies, or interventions carried out by the Soviet Union or its authorities toward 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a25760af348190bf402089c240887d |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564417848190a8a8a38e97348963 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.