Triple
T302034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sims-class destroyer |
E6217
|
entity |
| Predicate | navalArchitectureFeature |
P8584
|
FINISHED |
| Object | single-stack design |
—
|
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: single-stack design | Statement: [Sims-class destroyer, navalArchitectureFeature, single-stack design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalArchitectureFeature Context triple: [Sims-class destroyer, navalArchitectureFeature, single-stack design]
-
A.
navalAccess
Indicates that one entity has the right or ability to use another entity’s naval facilities, waters, or maritime routes for military or strategic purposes.
-
B.
hullType
chosen
Indicates the specific structural design or configuration of an object's hull, typically classifying how its outer body or shell is shaped or constructed.
-
C.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
D.
shipyard
Indicates a relationship where a location functions as a facility for building, repairing, or maintaining ships.
-
E.
mainTankFeature
Indicates that a feature is the primary or defining characteristic of a tank in the given 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea2fba548190a5aeb1597dca96bd |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93c367881908d3f6e2b81d44d7f |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.