Triple
T13285426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northampton-class cruiser |
E316430
|
entity |
| Predicate | navalGunCaliberCategory |
P6076
|
FINISHED |
| Object | 8-inch gun cruiser |
—
|
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: 8-inch gun cruiser | Statement: [Northampton-class cruiser, navalGunCaliberCategory, 8-inch gun cruiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalGunCaliberCategory Context triple: [Northampton-class cruiser, navalGunCaliberCategory, 8-inch gun cruiser]
-
A.
natoCaliberClass
Indicates that two ammunition types share the same standardized NATO caliber classification.
-
B.
gunCalibre
chosen
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
C.
navalStandardType
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
-
D.
torpedoCaliber
Indicates the specific diameter or size classification of a torpedo used in a given context or system.
-
E.
munitionWeightCategory
Indicates the classification of a munition based on its weight range or weight-related category.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:27 p.m.