Triple
T37330717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Leander |
E926735
|
entity |
| Predicate | antiAircraftArmamentUpgraded |
P118958
|
FINISHED |
| Object | 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: during World War II | Statement: [HMS Leander, antiAircraftArmamentUpgraded, during World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antiAircraftArmamentUpgraded Context triple: [HMS Leander, antiAircraftArmamentUpgraded, during World War II]
-
A.
enhancedArmament
Indicates that an entity’s weaponry or combat equipment has been upgraded, augmented, or otherwise improved beyond its standard configuration.
-
B.
aircraftDefensiveArmament
Indicates that an aircraft is equipped with weapons or systems specifically intended for its own defense against attacks.
-
C.
airDefenseArmament
chosen
Indicates the weapons or systems specifically equipped on an entity for defending against aerial threats such as aircraft or missiles.
-
D.
aircraftArmament
Indicates that an aircraft is equipped with a particular weapon or armament system.
-
E.
opponentAircraft
Indicates that one aircraft is an adversary or opposing aircraft relative to another in a conflict or competitive context.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.