Triple
T348361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Malta |
E6988
|
entity |
| Predicate | isSiegeOf |
P11070
|
FINISHED |
| Object | Malta during World War II |
—
|
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: Malta during World War II | Statement: [Battle of Malta, isSiegeOf, Malta during World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSiegeOf Context triple: [Battle of Malta, isSiegeOf, Malta during World War II]
-
A.
currentStronghold
Indicates that an entity currently serves as the primary base, fortress, or central stronghold for another entity.
-
B.
conquestEvent
Indicates an event in which one party gains control over another entity or territory through force or domination.
-
C.
conqueredCity
Indicates that one entity has taken control of a city from another entity, typically through military force or domination.
-
D.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
-
E.
encirclementOperation
Indicates a military action in which forces maneuver to surround an opposing force, cutting off its escape routes and lines of support.
- F. None of above. chosen
Provenance (4 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb1c1c908190b3a01de893207ed1 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e955d1f88190bd687c46fa7c5469 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea60e590819081779a6510918d9b |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.