Triple
T26882590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Courageous |
E676944
|
entity |
| Predicate | armamentAsCarrier |
P161978
|
FINISHED |
| Object | anti-aircraft guns |
—
|
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: anti-aircraft guns | Statement: [HMS Courageous, armamentAsCarrier, anti-aircraft guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armamentAsCarrier Context triple: [HMS Courageous, armamentAsCarrier, anti-aircraft guns]
-
A.
nuclearWarheadCarrier
Indicates that an entity is designed or used to carry, transport, or deliver nuclear warheads.
-
B.
armamentAsBuilt
Indicates the weaponry or armament configuration that an object (such as a vehicle, vessel, or structure) originally had when it was first constructed or completed.
-
C.
tertiaryArmament
Indicates the relationship where an entity possesses or is equipped with a third-level (tertiary) weapon or armament beyond its primary and secondary armaments.
-
D.
numberOfMissilePods
Indicates the quantity of missile pods associated with or mounted on an entity.
-
E.
plannedArmamentClass
Indicates that an entity is intended or designated to be equipped with a particular class or type of armament.
- 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f62081136c81909de8090b1d6c1ac5 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fd5442081908ca677a9c81dcb3f |
completed | May 2, 2026, 4:01 p.m. |
Created at: April 27, 2026, 5:40 a.m.