Triple
T25224343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California-class starship |
E632050
|
entity |
| Predicate | hasEngineeringHull |
P161448
|
FINISHED |
| Object | secondary hull |
—
|
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: secondary hull | Statement: [California-class starship, hasEngineeringHull, secondary hull]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEngineeringHull Context triple: [California-class starship, hasEngineeringHull, secondary hull]
-
A.
hullConstruction
Indicates the process or activity of building, assembling, or forming the main body (hull) of a vessel or similar structure.
-
B.
hullReinforcement
Indicates that an entity strengthens or protects the outer structure or hull of another entity, typically to increase its durability or resistance to damage.
-
C.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
D.
hasSeaArmType
Indicates that an entity is associated with or characterized by a specific type of sea arm (such as a bay, gulf, fjord, or similar marine inlet).
-
E.
hullWeight_kg
Indicates the weight of an object's hull measured in kilograms.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f613bc641c819084343cc78d080640 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f613502d808190b89927e5e734b43a |
completed | May 2, 2026, 3:08 p.m. |
Created at: April 21, 2026, 1:03 p.m.