Triple
T22283540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Dakota-class battleship |
E550799
|
entity |
| Predicate | hasHullNumberRange |
P11282
|
FINISHED |
| Object | BB-57 to BB-60 |
—
|
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-57 to BB-60 | Statement: [South Dakota-class battleship, hasHullNumberRange, BB-57 to BB-60]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHullNumberRange Context triple: [South Dakota-class battleship, hasHullNumberRange, BB-57 to BB-60]
-
A.
hullNumberRange
chosen
Indicates a relationship where an entity’s hull number falls within a specified numeric range.
-
B.
hasHullType
Indicates that an entity possesses or is characterized by a specific type or form of hull.
-
C.
hasPierNumberRange
Indicates that an entity is associated with a continuous range of pier numbers, from a starting pier number to an ending pier number.
-
D.
numberOfHulls
Indicates the quantity of distinct hulls that an entity possesses or is composed of.
-
E.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15605a8448190906a0ab9ffa4260b |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.