Triple
T27659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Navy |
E551
|
entity |
| Predicate | coreCapability |
P182
|
FINISHED |
| Object | sea-based nuclear deterrent |
—
|
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: sea-based nuclear deterrent | Statement: [United States Navy, coreCapability, sea-based nuclear deterrent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreCapability Context triple: [United States Navy, coreCapability, sea-based nuclear deterrent]
-
A.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
B.
coreIdea
Indicates the central concept or primary message that underlies or unifies something, such as a text, argument, or work.
-
C.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
D.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
E.
hasConcept
Indicates that an entity includes, embodies, or is associated with a particular concept.
- 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_69a243b4ac2c8190b93c303df797b7b2 |
completed | Feb. 28, 2026, 1:24 a.m. |
| NER | Named-entity recognition | batch_69a247798a348190bb943d38300ae3ef |
completed | Feb. 28, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69a24658749881909117b007ec3d8633 |
completed | Feb. 28, 2026, 1:35 a.m. |
Created at: Feb. 28, 2026, 1:34 a.m.