Triple
T37831355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Johnston (DD-821) |
E943210
|
entity |
| Predicate | namedAfterShipType |
P3141
|
FINISHED |
| Object | Fletcher-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: Fletcher-class destroyer | Statement: [USS Johnston (DD-821), namedAfterShipType, Fletcher-class destroyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterShipType Context triple: [USS Johnston (DD-821), namedAfterShipType, Fletcher-class destroyer]
-
A.
laterShipType
Indicates that one ship type chronologically succeeds or is introduced after another ship type.
-
B.
shipTypeProduced
Indicates that a particular type of ship is produced, built, or manufactured by a given entity.
-
C.
originalShipType
Indicates the type or category of ship that an entity was originally classified or built as.
-
D.
navalStandardType
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
-
E.
shipClass
chosen
Indicates the classification or type category to which a particular ship belongs.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 3, 2026, 4:19 p.m.