Triple
T25743332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSBN(X) program |
E648276
|
entity |
| Predicate | replacedClassName |
P165321
|
FINISHED |
| Object | Ohio-class |
—
|
NE NERFINISHED |
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: Ohio-class | Statement: [SSBN(X) program, replacedClassName, Ohio-class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedClassName Context triple: [SSBN(X) program, replacedClassName, Ohio-class]
-
A.
replacedClass
Indicates that one class has been superseded or substituted by another class, typically in a versioning or refactoring context.
-
B.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
C.
replacedPattern
Indicates that one pattern has been substituted or exchanged for another pattern in a given context.
-
D.
replacementName
Indicates that one entity serves as a substitute or successor name for another entity, effectively replacing the original designation.
-
E.
replacedInterface
Indicates that one interface has been substituted or superseded by another interface.
- F. None of above. chosen
Provenance (4 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 22, 2026, 3:47 a.m.