Triple
T38217551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lynx Wildcat |
E1010725
|
entity |
| Predicate | navalVariantDesignation |
P156484
|
FINISHED |
| Object | HMA2 |
—
|
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: HMA2 | Statement: [Lynx Wildcat, navalVariantDesignation, HMA2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalVariantDesignation Context triple: [Lynx Wildcat, navalVariantDesignation, HMA2]
-
A.
vesselDesignation
chosen
Indicates that a specific identifying designation (such as a name, number, or code) is assigned to a vessel.
-
B.
navalClassGeneration
Indicates that one naval class belongs to a particular generational sequence or iteration relative to another naval class.
-
C.
navalTechnologyType
Indicates the specific category or type of naval technology associated with an entity.
-
D.
navalStandardType
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
-
E.
navalName
Indicates that an entity has a specific name used in a naval or maritime 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.