Triple
T33988318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IX-300 |
E871471
|
entity |
| Predicate | navalDesignationType |
P156484
|
FINISHED |
| Object | unclassified miscellaneous vessel |
—
|
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: unclassified miscellaneous vessel | Statement: [IX-300, navalDesignationType, unclassified miscellaneous vessel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalDesignationType Context triple: [IX-300, navalDesignationType, unclassified miscellaneous vessel]
-
A.
USNDesignation
Indicates the formal designation assigned by the United States Navy to identify and classify a ship, aircraft, or other naval asset.
-
B.
vesselDesignation
chosen
Indicates that a specific identifying designation (such as a name, number, or code) is assigned to a vessel.
-
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.
navalName
Indicates that an entity has a specific name used in a naval or maritime context.
-
E.
fleetOrClass
Indicates that something belongs to, is part of, or is categorized under a particular fleet or class.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:50 a.m.