Triple
T8081510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee-class battleship |
E188625
|
entity |
| Predicate | navyDesignationPrefix |
P80388
|
FINISHED |
| Object | BB |
—
|
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: BB | Statement: [Tennessee-class battleship, navyDesignationPrefix, BB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navyDesignationPrefix Context triple: [Tennessee-class battleship, navyDesignationPrefix, BB]
-
A.
airForceDesignationPrefix
Indicates the specific prefix code assigned to an entity as part of an air force designation system.
-
B.
missionDesignationPrefix
Indicates the standardized prefix string used to label or identify a mission within a naming or designation system.
-
C.
USNDesignation
Indicates the formal designation assigned by the United States Navy to identify and classify a ship, aircraft, or other naval asset.
-
D.
navy
Indicates that an entity serves as or is associated with a nation's naval military force.
-
E.
aircraftDesignationPrefix
Indicates the standardized prefix used in an aircraft’s designation that conveys its type, role, or function.
- F. None of above. chosen
Provenance (4 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb40a699388190a5b8e26524ae43e5 |
completed | March 31, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:28 p.m.