Triple
T32682270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Midway (CV-41) |
E835617
|
entity |
| Predicate | NavyRegistryNumber |
P3152
|
FINISHED |
| Object | CVB-41 (original designation) |
—
|
NE NERFINISHED |
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: CVB-41 (original designation) | Statement: [USS Midway (CV-41), NavyRegistryNumber, CVB-41 (original designation)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NavyRegistryNumber Context triple: [USS Midway (CV-41), NavyRegistryNumber, CVB-41 (original designation)]
-
A.
NavyRegistry
Indicates a formal registration or listing of an entity within an official navy or naval organization.
-
B.
hullNumber
chosen
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
C.
USNDesignation
Indicates the formal designation assigned by the United States Navy to identify and classify a ship, aircraft, or other naval asset.
-
D.
USCGNumber
Indicates that an entity has been assigned a specific identification number by the United States Coast Guard.
-
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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c7e92f38819084db3081ae5de9ec |
completed | May 3, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:09 a.m.