Triple
T34703798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSGN |
E1000443
|
entity |
| Predicate | natoReporting |
P181711
|
FINISHED |
| Object | U.S. nuclear-powered guided-missile submarine |
—
|
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: U.S. nuclear-powered guided-missile submarine | Statement: [SSGN, natoReporting, U.S. nuclear-powered guided-missile submarine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natoReporting Context triple: [SSGN, natoReporting, U.S. nuclear-powered guided-missile submarine]
-
A.
natoReportingNameOfSystem
Indicates that one entity is the NATO reporting name assigned to a particular military system.
-
B.
NATOcode
Indicates that there is a specified NATO (North Atlantic Treaty Organization) code assigned to or associated with an entity.
-
C.
associatedWithNATO
Indicates a relationship in which an entity has a formal or recognized connection, affiliation, or involvement with NATO.
-
D.
militaryTheaterReportedOn
Indicates that a report or account has been made about a particular military theater or area of operations.
-
E.
NATOStandard
Indicates that something conforms to, is defined by, or is governed by standards established by NATO.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f7805c25dc8190b9977c561ba15975 |
completed | May 3, 2026, 5:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.