Triple
T30867929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yankee-class submarine |
E786254
|
entity |
| Predicate | hasSovietDesignation |
P18172
|
FINISHED |
| Object | Project 667A |
—
|
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: Project 667A | Statement: [Yankee-class submarine, hasSovietDesignation, Project 667A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSovietDesignation Context triple: [Yankee-class submarine, hasSovietDesignation, Project 667A]
-
A.
SovietDesignation
chosen
Indicates that an entity has been assigned an official designation or code name by Soviet authorities or according to Soviet classification systems.
-
B.
isSovietCounterpartOf
Indicates that one entity serves as the Soviet-era equivalent or counterpart to another entity in role, function, or status.
-
C.
russianDesignation
Indicates that one entity is the Russian-language name, label, or designation used to refer to another entity.
-
D.
usesSovietSymbols
Indicates that an entity employs or displays symbols associated with the former Soviet Union.
-
E.
returnedFromSovietUnion
Indicates that an entity came back from the Soviet Union to another place after having been there.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 29, 2026, 8:47 p.m.