Triple
T4633678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monastir |
E101476
|
entity |
| Predicate | heavilyBombardedBy |
P34756
|
FINISHED |
| Object | Central Powers artillery in World War I |
—
|
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: Central Powers artillery in World War I | Statement: [Monastir, heavilyBombardedBy, Central Powers artillery in World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heavilyBombardedBy Context triple: [Monastir, heavilyBombardedBy, Central Powers artillery in World War I]
-
A.
wasBombardedDuring
chosen
Indicates that an entity was subjected to a bombardment (e.g., shelling, bombing, or heavy attack) during a specified event or time period.
-
B.
bombed
Indicates that one entity attacked another using explosive weapons, causing or intending to cause destruction or damage.
-
C.
wasBombedDuring
Indicates that an entity was subjected to a bombing attack during a specified event or time period.
-
D.
wasBombedOn
Indicates that a location or target experienced a bombing event at a specific time or date.
-
E.
damagedBy
Indicates that one entity has caused harm, impairment, or deterioration to 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a5d0de881909baacc5b991f5b53 |
completed | March 20, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.