Triple
T1380404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Mexico class |
E29323
|
entity |
| Predicate | navalStandardType |
P27155
|
FINISHED |
| Object | U.S. Navy standard-type battleship concept |
—
|
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: U.S. Navy standard-type battleship concept | Statement: [New Mexico class, navalStandardType, U.S. Navy standard-type battleship concept]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalStandardType Context triple: [New Mexico class, navalStandardType, U.S. Navy standard-type battleship concept]
-
A.
shipClass
Indicates the classification or type category to which a particular ship belongs.
-
B.
fleetType
Indicates the category or classification of a fleet to which an entity belongs or with which it is associated.
-
C.
craftType
Indicates the specific kind or category of craft or vessel associated with an entity.
-
D.
tonnageClass
Indicates a classification relationship where an entity is assigned to a category based on its tonnage (weight or carrying capacity range).
-
E.
originalShipType
Indicates the type or category of ship that an entity was originally classified or built as.
- 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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c319f46481909ba8a69a19b865e5 |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4befe343c81909f758440a531b5be |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c0335f7081908d50046ced4cdee0 |
completed | March 1, 2026, 10:39 p.m. |
Created at: March 1, 2026, 7:59 p.m.