Triple
T25743341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSBN(X) program |
E648276
|
entity |
| Predicate | designatedClass |
P169221
|
FINISHED |
| Object | Columbia-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: Columbia-class | Statement: [SSBN(X) program, designatedClass, Columbia-class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatedClass Context triple: [SSBN(X) program, designatedClass, Columbia-class]
-
A.
designClass
Indicates that one entity is the design or blueprint class from which the other entity is derived or instantiated.
-
B.
destinationClass
Indicates the class or category that serves as the target or endpoint of a relationship or transition from another entity.
-
C.
isDesignatedAccordingTo
Indicates that an entity has a particular status, role, or classification as formally specified by a given authority, standard, or designation scheme.
-
D.
prototypeDesignation
Indicates that one entity is designated or identified as a prototype version or exemplar of another entity.
-
E.
designatorType
Indicates the specific role or category of a designator used to identify or reference an entity within a system or context.
- 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_69f67d691a948190afa7fb19ae7d4ac5 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67c9ec1708190b26ccf402ed7b106 |
completed | May 2, 2026, 10:37 p.m. |
Created at: April 22, 2026, 3:47 a.m.