Triple
T31305850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-700 Granit |
E798333
|
entity |
| Predicate | originatingMilitary |
P40599
|
FINISHED |
| Object | Soviet Navy |
—
|
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: Soviet Navy | Statement: [P-700 Granit, originatingMilitary, Soviet Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatingMilitary Context triple: [P-700 Granit, originatingMilitary, Soviet Navy]
-
A.
militaryOrigin
chosen
Indicates that an entity originates from, was created by, or is derived from a military organization, context, or background.
-
B.
countryMilitary
Indicates that a country possesses, controls, or is associated with a particular military force or armed organization.
-
C.
derivedFromMilitaryOrCivil
Indicates that something originates from, is based on, or is obtained through military or civil (non-military governmental) sources, activities, or contexts.
-
D.
militaryDomain
Indicates that the relationship or action occurs within, pertains to, or is specifically associated with the military sphere or context.
-
E.
militaryBacked
Indicates that one entity is supported, protected, or sustained by the military power or armed forces of another entity.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00a22e32f481909b6006c5b1cdefd3 |
completed | May 10, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_6a00a1bd9c908190b4aa17a61f48126f |
completed | May 10, 2026, 3:18 p.m. |
Created at: April 29, 2026, 9:14 p.m.