Triple
T35561841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Impero |
E1027654
|
entity |
| Predicate | designedAAArmament |
P159514
|
FINISHED |
| Object | 90 mm dual-purpose 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: 90 mm dual-purpose guns | Statement: [Impero, designedAAArmament, 90 mm dual-purpose guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedAAArmament Context triple: [Impero, designedAAArmament, 90 mm dual-purpose guns]
-
A.
weaponDesigner
Indicates that one entity is the creator or designer of a weapon used or associated with another entity.
-
B.
designedArmor
Indicates that one entity created or planned the armor used or worn by another entity.
-
C.
primaryArmament
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
-
D.
secondaryArmament
Indicates that one entity serves as a secondary or auxiliary weapon system associated with another primary platform or armament.
-
E.
armamentIncludes
chosen
Indicates that a larger weapon system, vehicle, or platform has a specified weapon or piece of equipment as part of its armament.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
Created at: May 3, 2026, 4:04 p.m.