Triple
T9005309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Benson (DD-421) |
E215127
|
entity |
| Predicate | isLeadShipOfClass |
P44837
|
FINISHED |
| Object | Benson-class destroyer |
—
|
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: Benson-class destroyer | Statement: [USS Benson (DD-421), isLeadShipOfClass, Benson-class destroyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLeadShipOfClass Context triple: [USS Benson (DD-421), isLeadShipOfClass, Benson-class destroyer]
-
A.
classLeadShip
chosen
Indicates a leadership relationship where one entity serves as the leading or primary representative of a class, group, or category.
-
B.
isTheHighestClassOf
Indicates that one entity represents the topmost or most advanced level within a hierarchy or classification to which the other entity belongs.
-
C.
hasShipRole
Indicates that an entity holds or is assigned a specific role or function on a ship.
-
D.
statusOfLeadShip
Indicates the current condition or state assigned to the primary or leading ship in a given context or operation.
-
E.
isEnsignFor
Indicates that one entity holds the rank or role of ensign in service to, or under the command of, another 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc695afa34819086cf6fcce2997b5f |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:05 p.m.