Triple
T1871503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benson-class destroyer |
E39044
|
entity |
| Predicate | hullConfiguration |
P8584
|
FINISHED |
| Object | flush-deck 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: flush-deck design | Statement: [Benson-class destroyer, hullConfiguration, flush-deck design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hullConfiguration Context triple: [Benson-class destroyer, hullConfiguration, flush-deck design]
-
A.
usedHullNumberSystem
Indicates that an entity employed a hull numbering system to identify or classify ships or vessels.
-
B.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
C.
hasHullType
Indicates that an entity possesses or is characterized by a specific type or form of hull.
-
D.
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.
-
E.
harborType
Indicates the specific kind or classification of a harbor associated with an entity.
- 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_69a8862f7074819096afe7fe65e179e9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb0f79fbc819085c54f3189a552d9 |
completed | March 7, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69abafe2b56c81909e13d543982e6e13 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.